iubenda Zapier integrationAutomate iubenda with Zapier.
The iubenda Zapier integration gives you 4 actions, 0 triggers and 0 searches. Another app, usually a form, starts the Zap, and iubenda records the consent, updates the subject or marks it verified once a double opt-in is confirmed.
Verified Trustpilot reviews · AI, automation & growth agency
What the iubenda Zapier integration does for you
It lets a Zap (one automation on Zapier: a starting event, then steps that run on their own) write into the iubenda Consent Solution. Every time someone signs up in another tool, iubenda gets a consent record with the email, the boxes ticked and the documents accepted, and nobody has to copy it across by hand.
Three outcomes cover most setups. A fresh consent record for each sign-up, built by Create a New Consent, which also opens the matching subject in the iubenda dashboard. A preference history that stays current when someone drops marketing emails but keeps the newsletter, through Update Preferences of a Subject. And a double opt-in trail you can show an auditor, closed by Verify a Subject once the person has confirmed.
Now the part the app page skips. iubenda has no trigger (the event that starts a Zap), so nothing that happens inside iubenda can set off an automation: the starting event always lives in another tool. There is no search step either (a step that looks up a record that already exists), which means a Zap cannot find a subject from its email. The Subject ID has to reach the step some other way, usually from the tool that starts the Zap.
If those two gaps decide the matter, the n8n vs Zapier and Make vs Zapier comparisons are the place to weigh the other platforms, and the Zapier review is the place to judge Zapier on its own.
Zapier vocabulary in one minute
Eight words you will meet in the editor, each in one plain line.
- Zap
- One automation on Zapier: a single starting event, then one or more steps that run every time that event happens.
- Trigger
- The event that starts a Zap. iubenda offers none, so with this app the trigger always sits in another tool, such as a form.
- Action
- The step that does the work once the Zap has started. Every iubenda action writes either a consent or a change to a subject.
- Task
- The unit Zapier bills: one action that completes successfully. A Zap running two iubenda actions per sign-up uses two tasks.
- Polling trigger
- A trigger Zapier checks on a timer. It asks the app for new items at a fixed interval, and that interval depends on your plan.
- Instant trigger
- A trigger the app reports by itself the moment the event happens, so nothing waits for the next check, on any plan.
- Filter
- A step that lets the Zap go on only when the incoming data meets your condition, for instance a ticked marketing box.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action turns a Zap into one, and it then needs a paid plan.
What a consent Zap really costs
The trigger never costs a task, and neither does Zapier checking for new entries. Only an iubenda action that succeeds is counted, so one sign-up recorded as one consent equals one task.
- Premium appNo, works on Free
- Free plan100 tasks a month, two-step Zaps
- Trigger cost0 tasks
- Failed actionNot counted
iubenda is not a premium app, so it runs on the free plan: 100 tasks a month and unlimited Zaps. The catch is size. A free Zap has two steps, one trigger and one action. Add a filter, or chain Verify a Subject after Create a New Consent, and the Zap turns multi-step, which needs a paid plan. A failed action is not counted. The grid below shows how often Zapier checks a polling trigger, and it matters here because your trigger sits in the other app.
Connect iubenda to Zapier in three steps
- 01
Open Apps and start a connection
A connection is your iubenda account linked to Zapier once, then reused by every step that touches iubenda. In your Zapier account, open the Apps page and click + Add connection.
- 02
Pick iubenda in the dialog
Type iubenda in the search box of the dialog that opens, select it, then click Add connection. A new browser tab appears on the iubenda side, where you sign in with the account that holds your consent records.
- 03
Sign in and grant access
Log in to iubenda in that tab and let Zapier access the account. You need an iubenda account of your own, plus write access to anything you do not own but want the Zap to fill. The connection then shows up in your list, ready for every Zap.
Your first Zap: from a newsletter form to an iubenda consent
GoalEach form entry with the marketing box ticked becomes a consent record in iubenda.
- 01
Start from your form
Create a new Zap and pick your form tool as the trigger app, with its new entry event. Test it: Zapier pulls the three most recent entries, so you map fields on a real one.
- 02
Add the filter
Click the plus icon under the trigger and choose Filter. Set the three boxes: the marketing field, a text rule, and the value your form sends when the box is ticked. This makes the Zap multi-step.
- 03
Add Create a New Consent
Add iubenda as the action app, choose Create a New Consent and select your connection. Map the email from the form into Email, which is the required field.
- 04
Fill only what the form asked
Map the consent boxes your form really showed (privacy policy, newsletter, terms, marketing) and leave the rest empty. Set Verified to False if the person still has to confirm by double opt-in.
- 05
Test, then publish
Run the action test and open the iubenda dashboard to see the new subject. Click Publish to switch the Zap on; from then on, each ticked entry adds a consent.
The 4 iubenda actions, by what they change
iubenda gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create a New Consent
ActionIn Zapier“This action will create a new consent in the iubenda Consent Solution. The new consent automatically creates a new subject, available in the relative section of the dashboard. Each consent action contains all the information necessary to uniquely identify that specific consent, the subject who performed it, the preferences expressed with that consent, the legal notices the user has accepted, the proof (e.g. the form the user was presented with). If you're trying to edit the preferences of an existing subject, use the "Update a subject" action instead.”
Writes a full consent record in iubenda from what your form collected: who agreed, to which legal documents, with which preferences. iubenda opens the matching subject in its dashboard without any extra step.
Update Preferences of a Subject
ActionIn Zapier“Update the preferences of a given subject in iubenda Consent Solution. Any change in preferences requires a new consent, therefore this action will create a new consent for the existing subject.”
Changes what an existing subject agreed to, say dropping marketing while keeping the newsletter. iubenda treats every change as a new consent, so the history keeps each version instead of overwriting the last.
Update a Subject
ActionIn Zapier“Use this action whenever you need to update a subject in the iubenda Consent Solution (e.g. change of the email address of the user). If you wish to update the preferences of a subject, you'll need to use the "Update preferences" action. Leave blank the fields you don't want to update.”
Edits who the subject is rather than what they agreed to, the classic case being a new email address. Fields you leave blank keep their current value in iubenda.
Verify a Subject
ActionIn Zapier“Use this action to update a subject when verified in iubenda Consent Solution, for instance via the double opt-in method. This action requires the subject has already been created.”
Marks a subject as verified once the person has confirmed, typically by clicking the double opt-in email. Only the Subject ID is required.
When your iubenda Zap breaks
Zapier links no help article to iubenda, so the cases below come from how the four actions are built and from limits that apply to every Zap.
Most failures trace back to a subject that does not exist yet or a Subject ID that never reached the step. When a Zap stops for a reason not listed here, the Zapier troubleshooting page walks through the checks in order.
Update or verify on a missing subject
Verify a Subject, Update a Subject and Update Preferences of a Subject all expect a Subject ID. If no consent created that subject first, the step has nothing to act on.Every preference change adds a consent
Update Preferences of a Subject records a new consent each time it runs. Firing it on every form edit, even with no real change, clutters the subject's history.Verified set too early
With double opt-in, Verified must stay False when the consent is created. Setting it True before confirmation gives the record a check that never took place.Old sign-ups stay out
A Zap only reacts to entries that arrive after it is switched on. Consents collected before you published stay out of iubenda until you move them as a separate job.A bulk import gets held back
When the form tool suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold the Zap back instead of writing every consent.One entry, one run
On a polling trigger, Zapier remembers the items it has already seen, so the same form entry never starts the Zap twice and never creates a second consent.
Need help automating iubenda with Zapier?
A person reads every message.
