Resources · Zapier integration

Grain Zapier integrationAutomate Grain with Zapier.

The Grain Zapier integration gives you 9 triggers, 1 action and 1 search. Every trigger is instant, so your calls reach the rest of your tools as soon as Grain records, edits or deletes something, even on the free plan of Zapier.

See the 11 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Grain Zapier integration actually does

Grain sits in your calls, records them and pulls out highlights and stories. Zapier is the layer that watches those events and does something with them. A Zap is the automation you build there: one event that starts it, then one or more steps that run each time that event happens.

On Grain, the integration is almost all listening. Nine of its eleven visible operations are triggers, and all nine are instant. Three outcomes come out of that.

A transcript on demand. Recording Added starts the Zap and the Get Transcript search fetches the text of that call, ready for whatever step comes next, so the exact words of the call travel with it instead of someone's memory of them.

A record of what changed. Highlight Updated, Recording Updated and Story Updated tell you when someone edits a highlight, a recording or a story after the meeting. Useful when a product researcher reworks the clips of an interview and the rest of the team needs to know.

A clean-up signal. The three Deleted triggers fire when a highlight, a recording or a story goes away, so a Zap can react instead of leaving stale references behind.

What Zapier does not do for Grain: there is no ready-made action to create a recording, a highlight or a story. The only action is API Request (Beta), a raw request you write yourself, aimed at Grain's own domains. If your plan was to push data into Grain, expect to work with the API directly. Before you commit, our Zapier review lays out where the platform is strong and where it is not.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this whole page. Here they are in plain English.

Zap
The automation you build on Zapier: one event that starts it, then the steps that run every time that event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
Action
What the Zap does once it has started: the step that writes, sends or moves something on your behalf.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Polling trigger
A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval and keeps only the ones it has not seen.
Instant trigger
A trigger the app reports itself. It calls Zapier the moment the event happens, so nothing waits for the next check. All of Grain's are instant.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set. Otherwise the run stops right there.
Search step
A step that looks up something that already exists in an app, so the steps after it can use what it found. Get Transcript is one.
Cost

What a Grain Zap costs you

Zapier bills tasks, not triggers. Watching Grain is free; only completed actions count.

  • Free plan tasks100 per month
  • Steps per Zap on Free2 (one trigger, one action)
  • Grain triggers9, all instant
  • Premium appNo

The trigger never costs a task, however many calls you record. Each action that succeeds counts once, so a Zap with three actions uses three times more than a Zap with one, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a filter or a search such as Get Transcript and the Zap becomes multi-step, which needs a paid plan. Grain itself is not a premium app, so it works from the free plan. The polling grid below does not slow Grain down, since all nine triggers are instant.

Connect

Connect your Grain account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your Grain account linked to Zapier once, then reused by every step that touches Grain.

  2. 02

    Find Grain

    Type Grain in the search box of the dialog and pick it, then click Add connection. You need an existing Grain account for this; Zapier does not create one for you.

  3. 03

    Sign in and allow access

    Sign in to Grain in the tab that opens and grant Zapier access to the account. If the Zap will touch recordings you do not own, make sure that account can read them first.

First Zap

Your first Zap: fetch the transcript of selected calls

GoalEach time Grain adds a new recording that matches your condition, pull its transcript so later steps can use it.

  1. 01

    Build: pick the trigger

    Start a new Zap, choose Grain as the app and Recording Added as the event, then pick the connection you just made. The lightning bolt next to it means the trigger is instant.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent recordings of the account, so pick a real call to map the following steps on.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, then in Configure & test set the field to look at, the rule and the value. Use a text rule for text: the wrong type is why a filter never passes.

  4. 04

    Add Get Transcript

    Add a step, open the SEARCH part of the Action event list and pick Get Transcript. Fill Recording ID with the value from the tested call and choose a Format.

  5. 05

    Test, then Publish

    Test each step once and read what came back. When the transcript looks right, click Publish to switch the Zap on. Remember: a filter plus a search means a paid plan.

Triggers

The 9 Grain triggers

9 events start a Zap when something happens in Grain, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Highlight Added

Instant trigger

In Zapier“Triggers when a Highlight is created.”

Someone clips a moment from a call and saves it as a highlight: this trigger hands that new highlight to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a sales lead marks a pricing objection during a demo and you want the clip logged where the whole team reviews objections.
Watch out
the transcript and the speakers ride along through two settings of the trigger, Include Transcript and Include Speakers; check them before you map anything.
2

Highlight Deleted

Instant trigger

In Zapier“Triggers when a Highlight is deleted.”

When a highlight disappears from Grain, this trigger lets the Zap know which one went, so you are not left with a link to nothing.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep a shared list of customer quotes and want a step that flags the entry whose source clip was removed.
Watch out
a Zap only sees deletions made after you publish it, so clips removed earlier never show up.
3

Highlight Updated

Instant trigger

In Zapier“Triggers when a Highlight is updated.”

Edits matter as much as new clips. Each change to an existing highlight starts the Zap with the edited version.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a researcher reworks a clip after the interview, and the copy in your research log should follow.
Watch out
it runs on every edit, so never let it create a new record each time; update an existing one instead, or you will collect duplicates.
4

Recording Added

Instant trigger

In Zapier“Triggers when a new Recording is created.”

The workhorse of the integration: a new call recorded by Grain becomes the starting point of your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every onboarding call with a new customer should land, with its notes, in the place your success team works from.
Watch out
highlights, participants, the calendar event, HubSpot data, AI action items, the AI summary and AI sections each have their own Include setting, so check the ones your next steps rely on.
5

Recording Deleted

Instant trigger

In Zapier“Triggers when a Recording is deleted.”

Removing a call in Grain can matter elsewhere. This trigger tells the Zap that a recording is gone.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a customer asks for a call to be erased and you want a step that alerts whoever keeps the account file, so nothing points to it anymore.
Watch out
Get Transcript cannot help after this event, since the recording it would read no longer exists in Grain.
6

Recording Updated

Instant trigger

In Zapier“Triggers when a Recording is updated.”

Recordings keep changing after the call ends. Any update to one of them sends the new state to your Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
an account manager corrects the participants of a renewal call and your notes should reflect the fix.
Watch out
each edit is a new run, so a Zap that creates something here will create it twice; point it at an update instead.
7

Story Added

Instant trigger

In Zapier“Triggers when a new Story is created.”

Stories are the third kind of item Grain exposes to Zapier, next to recordings and highlights. Creating a new one in Grain is what starts this Zap.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a product manager assembles the voice of the customer for a release review, and the team should hear about it without a separate message.
8

Story Deleted

Instant trigger

In Zapier“Triggers when a Story is deleted.”

Stories get retired too. This one fires when a story is removed, which keeps references to it honest.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your enablement library lists the stories reps should watch, and a removed one has to be flagged before someone clicks it.
Watch out
nothing that was deleted before the Zap went live will ever come through.
9

Story Updated

Instant trigger

In Zapier“Triggers when a Story is updated.”

Here the Zap follows the life of a story already made: every change to it sends the updated story along.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a marketer refines a story used in a launch brief and the reviewers need to know the version moved.
Watch out
a single editing session can mean several runs, so keep the action an update, never a creation.
Actions

The Grain action

Grain gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

This is the escape hatch: a raw HTTP request to Grain that reuses the connection you already made, for anything the triggers and the search do not cover.

When to use it
a developer on your team knows the Grain API call they need and wants it inside a Zap.
Watch out
HTTP Method, URL and Stop on error are required, and the URL must point to a domain tied to Grain.
Searches

The Grain search

1 search step looks for data that already exists in Grain, so a later step can use it.

A search step reads something that already exists in Grain and hands it to the next steps. It sits at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the lookup does not go as planned.

1

Get Transcript

Search

In Zapier“Fetch the Transcript of a recording”

Give it a recording and it returns the text of that call, so the next step can store it, quote it or send it on.

When to use it
right after Recording Added, when the trigger alone does not carry the transcript you need.
Watch out
Recording ID and Format are both required, and the connected account must be able to read that recording.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and skips the steps that relied on it. Switch it on and the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. Grain offers no such variant on Get Transcript, so you will not see it here.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on.
When it breaks

When a Grain Zap breaks

Zapier attaches no help article to Grain and lists no app-specific limit. What breaks is what breaks on any Zap.

Four situations account for most surprises. In the first three the Zap does not fail loudly: it simply does less, or more, than you expected. If you get stuck, our Zapier troubleshooting page is the next stop.

  • Old calls never show up

    A Zap only reacts to what happens after you publish it. Recordings made last month stay where they are; moving that backlog is a separate job.

  • The Zap keeps setting itself off

    If a step writes back into the place its own trigger watches, every run starts a new one. That loop burns through your task count fast.

  • A bulk change gets held back

    When a trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.

  • The API request is refused

    API Request (Beta) only reaches domains tied to Grain. With Stop on error set to Yes the step halts on an error; set to No it runs on regardless.
Need help

Need help automating Grain with Zapier?

A person reads every message.

FAQ

Grain Zapier integration: your questions

01Is the Grain Zapier integration free?
Yes, as long as the Zap stays at two steps. Grain is not a premium app, so it works on the free plan, which gives 100 tasks a month and unlimited Zaps. The catch is the step limit: one trigger and one action. A Zap that adds Get Transcript, a filter or a second action becomes multi-step, and that requires a paid plan. So a plain Recording Added to API Request (Beta) Zap is free, while the transcript Zap described above is not.
02How many tasks does a Grain Zap use?
One per successful action, and nothing for the trigger. Grain can record dozens of calls without costing you anything on the Zapier side until an action actually completes. In a Zap with three actions, each one that succeeds counts on its own, so the same run costs three tasks. An action that fails is not counted. Watching for new events never costs a task, whatever the plan, which is why a busy recording week does not empty your quota on its own.
03Is Grain on Zapier real time?
Yes. All nine Grain triggers are instant: Grain tells Zapier the moment a recording, a highlight or a story is added, updated or deleted, and the Zap starts right away. The polling intervals of the plans, 15 minutes on Free down to 1 minute on Team and Enterprise, do not apply to them. In the editor you will see a lightning bolt on these triggers, which is how Zapier marks an instant one.
04What does it take to connect Grain to Zapier?
Two things: a Grain account, and access to whatever the Zap should read. You add the connection from the Apps page with + Add connection, search for Grain, sign in in the tab that opens and grant access. If the Zap needs recordings owned by someone else, the connected account needs read access to them, otherwise steps like Get Transcript will not find them. Nothing else is required on the Zapier side: the connection is made once and every Grain step reuses it.
05Why does an Updated trigger create duplicates?
Because it fires on every edit, not once per item. Highlight Updated, Recording Updated and Story Updated each start a new run whenever someone changes the item, and one editing session can mean several changes. If the action creates a record, you get one record per edit. Point the Zap at updating an existing record instead, or use the matching Added trigger when the goal is to create something once per highlight, recording or story.
06What if the Grain operation you need does not exist?
Use API Request (Beta). It sends a raw HTTP request to Grain with the authentication of your connection, so anything the Grain API exposes can be called from a Zap. You set the HTTP Method, the URL and Stop on error yourself. The URL has to point to a domain tied to Grain. It assumes someone on the team is comfortable reading API documentation, and it is labelled Beta, so treat it as a tool to test carefully before you publish.
07Zapier, Make or n8n for Grain?
Decide on what you need from Grain, not on the brand. If your flows start from Grain events, Zapier covers nine of them, all instant, plus a transcript lookup, and the free plan handles simple two-step Zaps. If you mostly need to write into Grain, Zapier only offers a raw API request, so compare how each tool handles that call, what it bills per run and who on your team will maintain it.
Same platform

Other docs you might need on this stack.

Browse all integrations