Function Zapier integrationAutomate Function with Zapier.
The Function Zapier integration gives you 1 action, 0 triggers and 0 searches. One move, Predict, runs a cloud predictor on data another app hands over. Function never starts a Zap on its own, so something else always goes first.
Verified Trustpilot reviews · AI, automation & growth agency
What the Function Zapier integration actually does
It lets a Zap (an automation on Zapier that starts on one event, then runs one or more steps) send data to a Function predictor and get a prediction back. Function is the AI step in the middle. It cannot be the starting point, because Zapier lists no trigger for it, only the Predict action.
Think of it as a scoring desk you can bolt onto any app Zapier already knows. Three results people usually chase with it:
A scored form answer. A survey or signup arrives, Predict runs the predictor you picked by its tag, and the result lands next to the answer in a spreadsheet.
A labeled record. A new deal or ticket appears in another tool, Predict reads the text you mapped into it, and a later step writes the label back. Same action, different input.
A routed message. The prediction goes into a chat or email step, so the right person sees it without opening Function at all.
Now the limits. Zapier does nothing on the Function side except call a predictor. It cannot create or train one, it cannot list your predictors, and it only reaches cloud predictors. A predictor that lives anywhere else stays out of reach. There is no search either, so a Zap cannot look up an earlier prediction.
Comparing tools before you commit? The Make vs Zapier comparison is a good second read.
Zapier words, in one minute
Seven terms come back on this page. Each one is explained once, here, then used as is.
- Zap
- The automation you build: one event that starts it, then the steps that run every time that event happens again.
- Trigger
- The event in an app that starts the Zap. Function has none, so a form, a CRM or a sheet plays that role.
- Action
- What the Zap does after it starts: the step that writes, sends or, here, asks a predictor for an answer.
- Task
- The unit Zapier bills. One action that completes successfully counts as one task on your monthly allowance.
- Polling vs instant trigger
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it quietly otherwise.
- Connection
- Your Function account, linked to Zapier once and then reused by every step that needs to call one of its predictors.
What a Function Zap costs in tasks
Function is not a premium app, so it works on the free plan. The bill is counted in tasks, not in predictions.
- Premium appNo, free plan works
- Free plan100 tasks a month, two-step Zaps only
- Trigger checksFree, never billed
- Failed PredictNot counted
The trigger costs nothing, however often Zapier checks it. Each Predict that succeeds counts as one task, and a failed one is not counted. The free plan gives 100 tasks a month but stops at two steps: one trigger, one action. Add a filter or a second action to store the result, and the Zap becomes multi-step, which needs a paid plan. In practice, budget one task per record for Predict, plus one more for every step that stores or sends the result.
Connect Function to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need a Function account first, plus access to any predictor you do not own yourself but want the Zap to call.
- 02
Pick Function in the dialog
Type Function in the search box of the dialog, select it, then click Add connection. A new tab opens on the Function side so you can sign in with the account that holds your predictors.
- 03
Grant access
Sign in and allow Zapier to use the account. The connection now shows on the Apps page, and every Predict step you add later reuses it without asking again.
Your first Function Zap, step by step
GoalScore every new Typeform answer with a Function predictor and keep the result in Google Sheets.
- 01
Create the Zap
Start a new Zap and pick the app that starts it. Here a Typeform survey plays that part, since Function cannot open a Zap by itself.
- 02
Set and test the trigger
Choose the form, then test. Zapier brings back the three most recent answers, so you map fields from a real one rather than a blank example.
- 03
Add Predict
Add an action, pick Function, then Predict. Paste the tag of your cloud predictor, then fill the other fields the step shows with values from the Typeform answer.
- 04
Store the result
Add a Google Sheets row and map in what Predict returned. This third step makes the Zap multi-step, so it needs a paid plan.
- 05
Test, then publish
Run each step once and read what came back, starting with Predict. When the new row looks right in the sheet, click Publish to switch the Zap on.
The Function action in Zapier
Function gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Predict
ActionIn Zapier“Make an AI prediction with a predictor.”
Hands the data you mapped to one of your Function predictors and brings its prediction back into the Zap, ready for the next step to store or send.
When a Function Zap breaks
Zapier attaches no help article to Function and no app-specific limit is documented. What breaks comes from how Zaps work in general.
Most surprises show up on the first day, not the hundredth. These four cover them, and the Zapier troubleshooting page picks up from there.
Old records are never scored
Predict only ever sees answers submitted after the Zap is published. Answers that already existed stay unscored, and moving that backlog is a separate job.The Zap keeps setting itself off
If the trigger watches a sheet for new rows and the last step writes the prediction into a new row of that same sheet, the Zap restarts on its own result and burns tasks.A bulk import gets held back
When the trigger app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of running Predict on each.No double predictions
On a polling trigger, Zapier remembers what it has already seen, so the same record does not start the Zap twice and you do not pay twice for one prediction.
Need help automating Function with Zapier?
A person reads every message.
