Pocket → Attio: the recorder that already speaks webhook

Last updated 1 November 2026 · Nacho Lafuente, Attio Certified Expert

Pocket is the small MagSafe recorder from heypocket.com that more and more investors clip to the back of their phone. It records in-person meetings and, through a contact microphone, phone calls, then turns them into a summary and action items. (Not the read-it-later app. Mozilla shut that Pocket down in 2025.) Pocket has no Attio integration, and its built-in syncs point at Notion, Google Drive, OneDrive and task apps. What it does have is a public API and signed webhooks that carry the summary, the action items and the speaker names in one payload. That makes it one of the cleaner recorders to wire into Attio, as long as you handle the parts the webhook leaves to you.

Direction

Pocket → Attio (summaries, action items and speakers onto Companies, People and Deals)

Stack

Pocket webhooks, Pocket public API, n8n, Attio API

The what

What this integration actually does

When Pocket finishes processing a recording, it sends a summary.completed webhook. We verify the signature, find the meeting it belongs to, and write the summary as a note on the founder's company and the open deal, linked to the Attio meeting. Pocket's action items arrive already structured, with a title and a due date where it heard one, so they become Attio tasks without another AI pass. When someone edits or regenerates the summary in Pocket, the note in Attio is updated rather than duplicated. When nobody can be matched, the recording goes to a review list instead of disappearing.

The how

How we build it

1
Create a personal webhook in Pocket pointing at an n8n endpoint, and store the signing secret, which Pocket only shows once. For a whole team on Pocket Enterprise, use an organization-wide webhook so every partner's recordings arrive without per-person setup.
2
Verify the HMAC signature on every delivery against the raw request body, and reject anything unsigned.
3
Subscribe to summary.completed for the first write, and to summary.updated, summary.regenerated and action_items.updated to keep Attio in step afterwards.
4
Match on time, not title: use recordingAt and the duration to find the overlapping Attio meeting for the recorder owner's email, then resolve its participants to People, Companies and the open Deal.
5
Write the summary markdown as a note on the Company and the Deal, tied to the meeting and dated to the recording, and save the Attio note ID against the Pocket recording ID.
6
Create Attio tasks from Pocket's action items, assigned to the partner who recorded, and stamp a "Last touch" date so pipeline views reflect the meeting.

Under the hood

What lives inside the pipeline

Signature verification, with the secret kept in a secret manager and never pasted into the workflow itself.
Idempotency keyed on the recording and the event, because Pocket delivers at least once and retries failed deliveries.
Order-independent handling of speakers.labeled and summary.updated, which Pocket documents can arrive in either order.
Backdated notes, so a recording that synced days late still sits in the right place on the timeline.
A review list for recordings with no overlapping meeting, such as a hallway conversation at a conference.
A one-off backfill through the public API, which lists recordings by date range, so history from before the webhook lands too.

Hard-earned lessons

What we learned the hard way

Speaker names are not people. Pocket names speakers from what was said and from the calendar invite, but the payload carries names, not email addresses, and recordings with more than eight speakers are not named automatically. Match on the calendar and use names only as a tiebreaker.
Do not use the title for timing. The default title is a display string in the owner's local time and usually changes after processing. recordingAt is UTC from the device clock and stays right even when the device syncs later.
Late sync means late notes. Pocket records offline and processes when it reconnects to the phone, so a note can reach Attio days after the meeting. Date it to the recording, not the delivery.
At-least-once delivery means duplicates. Without an idempotency key, a retry writes a second note on the same deal.
A note never counts as an interaction in Attio. Last-interaction attributes fill from synced email and calendar only, so stamp your own "Last touch" date or stale-deal alerts keep firing.
Personal webhooks belong to one person. When a partner leaves or rotates the secret, their recordings stop arriving without an error. Organization-wide webhooks, or a simple heartbeat check, catch that. Older webhooks created without a secret can also keep sending unsigned until you rotate them.

Case study

Reference build for a VC platform team

Problem

Partners used Pocket for in-person founder meetings and phone calls. Summaries and action items lived in each partner's Pocket account, and the Deal records in Attio had none of it.

Solution

Signed Pocket webhooks into n8n, calendar overlap matching against Attio meetings, summaries as notes on Company and Deal, Pocket action items as Attio tasks, and a review list for unmatched recordings.

Outcome

Founder conversations sit on the Deal next to the rest of the diligence, follow-ups are tasks with owners, and the pipeline meeting starts from Attio instead of from memory.

FAQ

Questions we get

The Pocket AI recorder from heypocket.com, the MagSafe device that records meetings and phone calls and turns them into summaries and action items. Not Mozilla's read-it-later app, which shut down in July 2025.

No. Pocket's built-in integrations cover calendars, documents such as Notion, Google Drive and OneDrive, and task apps such as Linear, Asana and ClickUp. For Attio we use its public API and webhooks, which Pocket documents for exactly this kind of automation in n8n, Zapier or Make.

Not to start. Personal webhooks are set up per user inside the Pocket app. Organization-level API keys and webhooks are part of Pocket Enterprise, and they become worth it once several partners record, because one webhook then covers the whole team.

On the Attio side, Pocket is the simpler build: signed webhooks with structured action items, against Plaud's Zapier trigger. On the device side both record in-person meetings and phone calls. Pick the recorder your partners will actually carry. We build either.

Yes, and for funds it usually should. We write to the Company and to the open Deal in your pipeline list, and only to the Person when there is no company yet, as with an early angel intro or a scout referral.

Pocket says recordings are encrypted in transit and at rest and hosted in the US, which matters for EU funds. Tell people before you record, keep full transcripts out of Attio unless you need them, and run n8n self-hosted so the payload is not stored by another vendor.