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. Set config.workspaceName in config.ts to the name of your Attio workspace
5. For each list you want to get notifications about, add an object to the config.lists array in config.ts. This object must contain a listId, notificationHeader, and objectName.
   1. To find your list's id, navigate to the list and copy the path segment after collection: https://app.attio.com/<workspaceName/collection/<listId>.
   2. The notificationHeader is the header that will appear in slack.
   3. objectName is the singular name of the object that list entries in the target list are a instances of. If you're unsure, navigate to the record for one of the list entries and copy the path segment after your workspace's name: https://app.attio.com/<workspaceName/<objectName>/<record_id>
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 another listConfig object to the lists array in config.ts the same way as you did in step 5, above.

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

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.