This val summarizes recent events on Attio lists on Slack.

This project receives Attio webhooks, verifies and processes them, and stores events, messages, and list entry state data in SQLite. A scheduled cron job uses then periodically sends summaries with these stored messages to Slack.

1. Remix this val
2. Get a Slack webhook & set it as SLACK_WEBHOOK_URL in this val's Environment variables in the left sidebar
3. Get an Attio Access Token (with all read & write permissions) & set it as ATTIO_API_KEY in this val's Environment variables in the left sidebar
4. Configure your lists in webhook.ts:
   • Update the listIds array with your Attio list IDs
   • To find your list's id, navigate to the list and copy the path segment after collection: https://app.attio.com/<workspaceName>/collection/<listId>
5. (Optional) Customize attribute extractors in webhook.ts:
   • Modify the customExtractors object to customize how attribute values are formatted in Slack messages
   • See the "Customizing Attribute Extractors" section below for details
6. Go to setup.ts and click run to set up the events database and Attio webhook
7. Go to alert.ts and click run to set up the cron job
8. Go trigger some Attio events and see the message in Slack!

If you want to get notifications about more than one list from your workspace, simply add the list ID to the listIds array in webhook.ts.

Then, go to bootstrap.ts and run the script. This will initialize the new list in SQLite.

This template provides a flexible system for customizing how Attio attribute values are formatted in Slack messages. You can override any of the built-in extractors or add custom formatting.

The easiest way to customize extractors is directly in the webhook.ts file:

// webhook.ts
export const customExtractors: CustomExtractors = {
   // Add emojis to text values
   text: (value) => `✨ ${value.value} ✨`,

   // Format status with custom styling
   status: (value) => `🔸 ${value.status.title}`,

   // Format currency with custom symbols
   currency: (value) =>
      `💰 ${Intl.NumberFormat("en-US", {
         style: "currency",
         currency: value.currency_code,
      }).format(Number(value.currency_value))}`,

   // Format dates with custom format
   date: (value) =>
      new Date(value.value).toLocaleDateString("en-US", {
         year: "numeric",
         month: "long",
         day: "numeric",
      }),
};

You can customize any of these Attio attribute types:

Common Types:

• text - Simple text values
• status - Status values with titles
• select - Dropdown/select values with option titles
• date - Date values
• timestamp - Timestamp values
• rating - Numeric rating values
• checkbox - Boolean checkbox values
• currency - Currency values with proper formatting
• record-reference - References to other records (fetches record name)
• actor-reference - References to users/actors (fetches actor name)

Uncommon Types:

• domain - Domain values
• email-address - Email address values
• interaction - Interaction values with type and timestamp
• location - Location values with address formatting
• number - Numeric values
• personal-name - Personal name values
• phone-number - Phone number values

For more complex customizations, you can:

1. Override extractors programmatically:

   import { overrideExtractors } from "./extractors/index.ts";
   
   overrideExtractors({
      text: (value) => `✨ ${value.value} ✨`,
   });

2. Pass custom extractors to functions:

   import { handleWebhookEvent } from "./services/webhook-handler.ts";
   
   const customExtractors = {
      text: (value) => `Custom: ${value.value}`,
   };
   
   await handleWebhookEvent(event, listIds, customExtractors);

3. Use the bootstrap function with custom extractors:

   import { initialize } from "./scripts/bootstrap.ts";
   
   await initialize(customExtractors);

Here are some common customization patterns you can use as templates:

export const customExtractors: CustomExtractors = {
   text: (value) => `📝 ${value.value}`,
   status: (value) => `🔸 ${value.status.title}`,
   select: (value) => `📋 ${value.option.title}`,
};

export const customExtractors: CustomExtractors = {
   currency: (value) => `💰 $${value.currency_value.toLocaleString()}`,
   number: (value) => `🔢 ${value.value.toLocaleString()}`,
   rating: (value) => `⭐ ${value.value}/5`,
};

export const customExtractors: CustomExtractors = {
   date: (value) => `📅 ${new Date(value.value).toLocaleDateString()}`,
   timestamp: (value) => `⏰ ${new Date(value.value).toLocaleString()}`,
};

export const customExtractors: CustomExtractors = {
   checkbox: (value) => (value.value ? "✅ Yes" : "❌ No"),
};

export const customExtractors: CustomExtractors = {
   "email-address": (value) => `📧 ${value.email_address}`,
   "phone-number": (value) => `📞 ${value.original_phone_number}`,
   "personal-name": (value) => `👤 ${value.full_name}`,
};

export const customExtractors: CustomExtractors = {
   location: (value) => {
      const parts = [
         value.line_1,
         value.locality,
         value.region,
         value.country_code,
      ].filter(Boolean);
      return `📍 ${parts.join(", ")}`;
   },
   domain: (value) => `🌐 ${value.domain}`,
};

export const customExtractors: CustomExtractors = {
   // Custom currency formatting with different symbols
   currency: (value) => {
      const symbol =
         value.currency_code === "USD"
            ? "$"
            : value.currency_code === "EUR"
            ? "€"
            : value.currency_code === "GBP"
            ? "£"
            : value.currency_code;
      return `${symbol}${Number(value.currency_value).toLocaleString()}`;
   },

   // Custom date formatting with relative time
   date: (value) => {
      const date = new Date(value.value);
      const now = new Date();
      const diffInDays = Math.floor(
         (now.getTime() - date.getTime()) / (1000 * 60 * 60 * 24)
      );

      if (diffInDays === 0) return `📅 Today`;
      if (diffInDays === 1) return `📅 Yesterday`;
      if (diffInDays < 7) return `📅 ${diffInDays} days ago`;

      return `📅 ${date.toLocaleDateString()}`;
   },

   // Custom status formatting with colors
   status: (value) => {
      const status = value.status.title.toLowerCase();
      if (status.includes("active") || status.includes("open"))
         return `🟢 ${value.status.title}`;
      if (status.includes("pending") || status.includes("waiting"))
         return `🟡 ${value.status.title}`;
      if (status.includes("closed") || status.includes("completed"))
         return `🔴 ${value.status.title}`;
      return `⚪ ${value.status.title}`;
   },
};

1. Copy any of the examples above
2. Paste them into your webhook.ts file, replacing the empty customExtractors object
3. Uncomment and modify the extractors you want to customize
4. Save the file and your customizations will be applied automatically

You can customize any of these Attio attribute types:

Common Types:

• text - Simple text values
• status - Status values with titles
• select - Dropdown/select values with option titles
• date - Date values
• timestamp - Timestamp values
• rating - Numeric rating values
• checkbox - Boolean checkbox values
• currency - Currency values with proper formatting
• record-reference - References to other records (fetches record name)
• actor-reference - References to users/actors (fetches actor name)

Uncommon Types:

• domain - Domain values
• email-address - Email address values
• interaction - Interaction values with type and timestamp
• location - Location values with address formatting
• number - Numeric values
• personal-name - Personal name values
• phone-number - Phone number values

To format custom Attio attribute types in your Slack messages, create a new formatter in the formatters/ directory:

// formatters/custom-formatter.ts
export function customFormatter(value: CustomAttributeValue): string {
   return value.customField;
}

Then import and use it in your message building logic.

The Slack message formatting is handled in shared/slack.ts. You can customize:

• Message headers and structure
• Link formatting
• Text truncation
• Message grouping logic

To handle additional Attio webhook event types:

1. Add the event type to types/webhook.ts
2. Create a new event handler class in services/webhook/handle-webhook.ts
3. Register it in the eventHandlers array

If you need to modify the database schema:

1. Update database/schema.ts with your new table/index definitions
2. Run the migration by executing createTables() in a script
3. Update the corresponding TypeScript types

The project uses these environment variables:

• ATTIO_API_KEY - Your Attio API access token
• SLACK_WEBHOOK_URL - Your Slack webhook URL

The project includes retry logic for API calls and comprehensive error logging. You can customize retry behavior in shared/retry.ts.

API responses are cached for 5 minutes to reduce redundant calls. Cache behavior can be modified in shared/cache.ts.

This project is designed to run on Val Town. To deploy:

1. Fork this val on Val Town
2. Set environment variables in the Val Town interface:
   • ATTIO_API_KEY - Your Attio API access token
   • SLACK_WEBHOOK_URL - Your Slack webhook URL
3. Run setup scripts in order:
   • scripts/setup.ts - Creates database and webhook
   • scripts/bootstrap.ts - Seeds initial data
4. Set up the cron job by running alert.ts and scheduling it
5. Test the webhook by triggering some Attio events

Required environment variables:

• ATTIO_API_KEY - Attio API access token with read/write permissions
• SLACK_WEBHOOK_URL - Slack incoming webhook URL

The application provides health check endpoints:

• GET / - Basic health status
• GET /health - Detailed health information

Monitor these endpoints to ensure the service is running correctly.

Webhook not receiving events:

• Verify the webhook URL is correct in Attio
• Check that the webhook is enabled for the right event types
• Ensure the webhook secret is properly configured

Slack messages not appearing:

• Verify SLACK_WEBHOOK_URL is set correctly
• Check Slack webhook permissions
• Review logs for error messages

Database issues:

• Run scripts/setup.ts to recreate tables
• Check Val Town SQLite storage limits
• Verify database indexes are created properly

attio-slack-summaries/
├── webhook.ts                   # Main HTTP endpoint - receives Attio webhooks
├── alert.ts                     # Cron job - processes recent events & sends Slack summaries
├── services/
│   ├── alert/
│   │   └── process-alerts.ts    # Alert processing logic
│   ├── attio/
│   │   ├── webhook.ts           # Attio webhook management - creates/stores webhook configs
│   │   └── utils.ts             # Attio API utilities & helpers
│   └── webhook/
│       └── handle-webhook.ts    # Webhook event processing logic
├── shared/
│   ├── slack.ts                 # Slack integration - message formatting & webhook sending
│   └── enrich-state.ts          # Data enrichment for CRM entries
├── types/
│   ├── index.ts                 # Core application types
│   ├── webhook.ts               # Attio webhook payload type definitions
│   └── attribute-values.ts      # Attribute value type definitions
├── database/                    # Data persistence layer
│   ├── schema.ts                # SQLite table definitions (events, messages, entries)
│   └── sqlite.ts                # Database operations - CRUD for webhook events & messages
└── scripts/
    ├── setup.ts                 # One-time setup - creates DB tables & Attio webhook
    └── bootstrap.ts             # Bootstrap script for initial setup

Attio webhooks return thin events, which contain a bunch of IDs, but no human-readable data, such as:

{
   "event_type": "record.merged",
   "id": {
      "workspace_id": "b6c564a6-2cf7-49ab-9320-dea013196bd7",
      "object_id": "a87cf74e-5ca1-4a8d-b8d3-fcca5413d4c3",
      "record_id": "d64ff9f2-d1f1-424c-8be6-e41129e35697"
   },
   "duplicate_object_id": "a87cf74e-5ca1-4a8d-b8d3-fcca5413d4c3",
   "duplicate_record_id": "112b5c78-1ffe-457a-8366-181b482888b4",
   "actor": { "type": "system", "id": null }
}

The trickiest part of this val was transformning these events into data that could be used to track the state of entries in lists. I've accomplished this here by storing the state of each entry in a SQLite database and then comparing subsequent states to the previous state of the entry to determine the changes.

These state objects are then used to generate message objects that are also stored in the SQLite database. When the cron job runs, it takes these message objects formats them into a nice payload and sends them to Slack.