[ Zapier ]
Every follow-up, as its own row.
Zapier connects Scriben to more than 9,000 apps, so what a meeting produced lands on the record you actually keep — a matter, a deal, a candidate file, a board — without anyone copying it across. Three triggers, two searches, one action. The transcript never moves.
New Meeting NoteTrigger. A meeting note is finished — title, summary, follow-ups, and who was there.New Action ItemTrigger. Scriben extracts a follow-up. Once per item, not once per meeting, so a meeting that produced four commitments creates four tickets.New MemoryTrigger. Scriben records a durable fact about a person, account or project.Find a Meeting NoteSearch. Finds a note by title, newest match. Takes a search term.Find a PersonSearch. What Scriben knows about someone across every meeting they were in. Takes a name.Create Share LinkAction. Publishes a note as a page anyone can open, and returns the link. Takes a note ref.Why New Action Item is the one to build first
Most meeting tools hand you the note and leave you to parse it, which is why so many Zaps end with an AI step re-deriving structure the tool already had. Scriben stores follow-ups as their own records, so Zapier can treat each as a row: one Linear issue per commitment, with its owner and its meeting attached — not a paragraph pasted into a description field.
[ Connecting ]
One approval. No key to copy.
Nothing to generate, paste or store. The approval creates a credential Zapier holds server-side, and you can revoke it from Scriben at any time.
In Zapier, create a Zap and search for Scriben. Pick a trigger.
Choose Connect a new account. Scriben opens in a window — sign in and approve.
The window closes and the account is connected. Add the app you want to write to.
What the approval grants
Read access to your notes, follow-ups, people and memories, and permission to create share links. Nothing else. The connection cannot edit or delete a note, cannot change your settings, and cannot reach another person's account — so an administrator connecting Zapier is not connecting the team. Each person authorises their own account and sees only their own data.
Any Scriben account works, on any Zapier plan. Once connected, Zapier checks for new notes on an interval set by your Zapier plan, not by Scriben.
[ Payload ]
Flat, typed, and always present.
Zapier learns the field list from the first payload it sees and permanently hides anything missing from it. So every field below arrives on every run — empty rather than absent when there is no value.
Lists ship twice: as an array for line-item steps, and as a newline-joined
_text version, which is what most Zaps actually drop into a note field. Each also
carries a _count, because a Zapier filter cannot measure an array's length —
without it, "only file meetings that produced follow-ups" is impossible to express.
New Meeting Note · Find a Meeting Note
| Field | What it is |
|---|---|
| id, ref | The note's identifier. Pass ref to Create Share Link. |
| title | The meeting's title. |
| type | The kind of meeting Scriben assigned — "Client call", "Standup". This is the field to branch on in a Filter or Paths step. |
| status | ready or failed. Filter on it if you do not want failed recordings filed. |
| date | When the meeting was recorded. ISO-8601, so Zapier parses it as a real date. |
| summary | The summary, as plain text. |
| action_items action_items_text action_items_count | The follow-ups from this meeting. |
| participants participants_text participants_count | Who was there, where Scriben could resolve real names. |
New Action Item
| Field | What it is |
|---|---|
| id | Stable identifier for this follow-up. |
| text | The follow-up itself. |
| note_ref note_title note_type | The meeting it came from, so the task can link back. |
| date | When that meeting was recorded. |
New Memory
| Field | What it is |
|---|---|
| id | Stable identifier for the memory. |
| subject | Who or what it is about. |
| text | The fact itself. |
| created_at | When Scriben recorded it. ISO-8601. |
Find a Person
Returns id, status, name, email,
org and context. When a name matches more than one person,
status is ambiguous, the identity fields come back
empty, and candidates lists who it could have been. A Zap mapping
email then writes a visible nothing rather than the wrong person's address, and a
Filter on status routes those to a human. Blending two people into one confident
answer is the failure we refuse to ship.
Create Share Link
Returns url, id, token, title and
expires_at. The link opens a readable recap for people who do not use Scriben —
useful on a record whose readers are outside your team. It refuses to publish a note that has
neither a summary nor any follow-ups, rather than minting a link to an empty page.
[ Boundaries ]
What never leaves your account.
The transcript and the audio
Not on a trigger, not on a search, not on a share link. There is no field to map them into and no option to turn them on. Scriben reads the transcript to work out who was speaking; what it passes on is the names.
A name it had to guess
Participants lists only people Scriben could resolve from the conversation. Where it cannot, the field is empty — never a placeholder like "Speaker 1". A wrong name attached to a meeting is worse than no name at all.
Markdown
Prose arrives as plain text. Markdown renders in perhaps a fifth of the places a Zap writes to and shows literal asterisks in the rest — a spreadsheet cell, a CRM description, a case note. Plain text is the only choice correct everywhere.
Anyone else's data
The credential is scoped to the account that approved it. There is no organisation-wide grant and no way for one connection to reach another person's meetings.
[ Zaps ]
The same payload, mapped six ways.
None of these fields is named matter, deal or
candidate. One shape, and the mapping to your vocabulary is what Zapier is for.
Action item → LinearEvery commitment becomes a ticket, with the meeting on it. Also Jira, Asana, Monday. The one to build first.Note → SlackPost the summary and follow-ups to a channel. Filter on type so only client calls go out.Note → HubSpotLog the meeting against the record. Add Create Share Link as a second step so colleagues without Scriben can read the recap. Also Salesforce.Note → SheetsA running log of every meeting, searchable by anyone. Also Notion, Google Docs.Memory → your CRMDurable facts about an account — who decides, what they use, when the contract ends — accumulating on the record instead of in someone's head.Note → ClioFile the recap on the matter. The same trigger a recruiter points at Greenhouse.[ Troubleshooting ]
Four things that look broken and are not.
Never runsTriggers do not fire on notes that already existed when you switched the Zap on — Zapier records them as seen so your first run does not produce a hundred tickets. Record something new, or use Test trigger to check the connection.Nothing appearingZapier checks on an interval set by your plan; a few minutes is normal. A note still processing in Scriben is not sent until it finishes — a Zap dedupes on the note, so firing on a half-built one would spend the only notification that meeting will ever get.Participants emptyScriben only lists people it could name from the conversation. See Boundaries.Asked to reconnectThe credential was revoked or expired. Reconnect the account in the Zap's trigger step; nothing else needs changing.Disconnecting
Either of these ends access immediately, and either is sufficient. From Zapier:
App connections → Scriben → Delete. From Scriben: Settings → Developer, find
the grant labelled Zapier, revoke it. Revocation applies to the very next request.
Questions: contact us, or read the HTTP API if you would rather call Scriben directly.