Attio
Connect Attio to import CRM people as leads, push leads back from Pana, and keep records in sync with optional webhooks.
What you get
- Import Attio contacts (people with email) as leads on a chosen Pana event.
- Limit how many contacts to import (all, 100, 200, or a custom number).
- Optional auto-sync so Pana keeps pulling contacts to a default event on a schedule.
- Push to Attio from the Leads page — single lead or bulk.
- Copy a webhook URL so updates in Attio can flow into Pana.
Attio is one connection per workspace. Click Connect and approve access in Attio — you do not create your own Attio app.
Fields Pana adds to Attio
When you connect, Pana sets up seven attributes on the Attio People object so you never have to create them by hand:
| Attio attribute | Type | What Pana writes |
|---|---|---|
| Lead Source | Text | Always Pana Events, so leads from Pana are easy to identify in Attio. |
| Event Name | Text | The event the lead is mapped to. |
| Event Lead Interest Level | Select — Cold, Warm, Hot | The lead's interest level from Pana. |
| Event Lead Tags | Multi-select — Exhibitor, Sponsor, Investor, Partner, High Priority, Decision Maker, Urgent, VIP | The lead's tags. A lead marked as a decision maker always carries Decision Maker. |
| Event Conversation Notes | Text | The latest note on the lead. Each push replaces it with the newest note. |
| Next Follow-up Date | Date & time | When the lead is due a follow-up, with the time of day. |
| Pana Lead URL | Text | A link back to the lead in Pana. |
These seven are the only attributes Pana creates. The lead's LinkedIn profile goes to Attio's built-in LinkedIn attribute, so nothing is created for it. If your workspace already has an attribute with one of these names, Pana reuses it instead of creating a duplicate — so reconnecting Attio is always safe.
Earlier versions of this integration created Lead Status, Lead Tag, Lead Notes and Event Source, and a date-only Next Follow-up Date. Connecting archives them in Attio, so a workspace that connected before this change ends up with the seven attributes above only. Archived attributes keep their history in Attio; nothing is written to them again.
Because Attio cannot change an attribute's type, the date-only Next Follow-up Date is replaced by a new date-and-time one rather than converted. The old column is archived with its values intact, and the new column fills up from the next push.
Next Follow-up Date needs your event's timezone set. Attio shows a time in each reader's own zone, so Pana converts the follow-up time before sending it. Set the timezone on your event (or the PANA_DEFAULT_TIMEZONE setting) to the zone your team works in — otherwise a 9:00 AM follow-up is sent as 9:00 UTC and reads as 2:30 PM to anyone in IST.
These fields are filled in on every single and bulk push, and are read back when you sync leads from Attio into Pana.
Before you start
- An Attio workspace where you can authorize apps.
- At least one event in Pana to attach synced leads to.
- Workspace admin access in Pana.
Connect Attio
- Go to Settings → Integrations.
- Find Attio under CRM.
- Click Connect.
- Sign in to Attio and approve the requested access.
- Return to Pana when authorization completes.
Sync leads
- On the Attio card, click Sync leads.
- Select a Pana event.
- Optionally choose an import limit (all contacts with email, or a fixed number).
- Optionally check Use this event for automatic sync.
- Click Sync.
Sync runs in the background. Contacts without an email address are skipped. Results appear as leads on the selected event; existing leads matched by Attio ID or email are updated.
Event Lead Interest Level, Event Lead Tags, Event Conversation Notes and Next Follow-up Date come back with the contact, along with the built-in LinkedIn attribute, so edits made in Attio show up on the Pana lead. Tags Pana does not provision are left on the lead untouched. Lead Source, Event Name and Pana Lead URL are set by Pana and are not read back — the event a lead belongs to is the one you picked for the sync.
Push leads to Attio
Use this when leads were captured in Pana and you want them in Attio.
Single lead
- Open Leads.
- On a lead row, use Push to Attio.
- Pana links or creates the matching person in Attio (email is required) and fills in Lead Source, Event Name, Event Lead Interest Level, Event Lead Tags, Event Conversation Notes, Next Follow-up Date, Pana Lead URL and LinkedIn.
Bulk push
- Select one or more leads in Leads.
- Use Push to Attio from the toolbar.
Webhooks
Pana registers its webhook in Attio for you when you connect, so person changes in Attio sync into Pana without a manual sync. Every call is checked against the webhook's signing secret, and anything unsigned is ignored. If it could not be registered at connect (for example, a self-hosted Pana without a public https API_BASE_URL), click Register webhook on the Attio card; registering again replaces the old webhook rather than adding a second one. The URL, for reference:
Webhook format:
https://eventsapi.pana.space/api/v1/integrations/webhooks/attio/{workspace_id}/
Disconnect
Turn off the toggle on the Attio card. Auto-sync stops; existing leads in Pana are kept.
Troubleshooting
| Issue | What to try |
|---|---|
| No events in the sync dialog | Create an event under Events first. |
| Contacts skipped | Attio people need an email address to import. |
| Sync still running | Large imports run in the background — wait a few minutes, then refresh Leads. |
| Push failed | Confirm the lead has an email and that Attio is still connected. |
| Pana's fields missing in Attio | Disconnect and reconnect Attio — Pana recreates any of its attributes that were deleted. |
| Old Pana fields still in Attio | Reconnect Attio. Archiving needs the read-write object configuration permission; if it is refused, archive Lead Status, Lead Tag, Lead Notes and Event Source by hand in Attio. |
| OAuth failed | Complete authorization in the same browser session; try disconnecting and connecting again. |