- Home
- Resources
- Integrations
- Adrapid
Adrapid Zapier integrationAutomate Adrapid with Zapier.
The Adrapid Zapier integration covers 1 trigger, 2 actions and 0 searches. Data from another tool can produce Adrapid banners in image, HTML5 or video form, and a finished banner can kick off the next step, such as a review or a delivery.
Verified Trustpilot reviews · AI, automation & growth agency
What the Adrapid Zapier integration does
Adrapid turns a template into banners, as still images, animated HTML5 or video. Zapier lets other tools feed it and react to it. It works in both directions: Zapier can ask Adrapid for a banner, and Adrapid can tell Zapier when a banner is ready to be sent on.
Three results people typically build. Banners from a product list: an online wine shop adds a row to its catalog sheet and Create Banner produces the visuals in every format picked. A ready banner, handed over: Banner Ready starts a Zap when Adrapid finishes one, so an event organizer can send it to the sponsor without opening Adrapid. The final file, fetched later: Get Banner retrieves a banner by its ID once it has had time to render, which is how a Zap picks up the result of an earlier creation.
What Zapier does not do here: it cannot edit a template, delete a banner or list your templates. There is no search step, so a Zap cannot look up a banner by name; it needs the ID. And Banner Ready is a polling trigger, so on the free plan expect up to 15 minutes before the Zap notices.
For a broader look at the tool, the Zapier review and Make vs Zapier are the two pages worth opening next.
Zapier terms, quickly
Seven words show up all over this page. Plain definitions first.
- Zap
- An automation built on Zapier: one trigger to start, then one or more actions that run every time that event happens.
- Trigger
- The event in an app that starts a Zap. While the Zap is on, Zapier keeps waiting for it to happen.
- Action
- What the Zap does once it starts: the step that writes, sends or moves something for you, like creating a banner.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your monthly plan is a count of these.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is pushed by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets your rule, and stops it otherwise.
- Connection
- Your Adrapid account linked to Zapier once, then reused by every step that creates or fetches a banner.
What a banner really costs in tasks
Adrapid is not a premium app, so the free plan can use it.
- Free plan100 tasks a month
- Free plan Zap size1 trigger + 1 action
- Premium appNo
- Banner ReadyPolling
Banner Ready costs nothing by itself, and neither do Zapier's checks for new banners. Create Banner and Get Banner each cost one task when they succeed; a failed one is not counted. The free plan gives 100 tasks a month and allows only two-step Zaps. So a Zap that creates a banner and then fetches it, with two actions, is multi-step and needs a paid plan.
Concretely, a Zap that emails the client for each finished banner uses one task per banner.
Connect Adrapid to Zapier in 3 steps
- 01
Go to Apps
Open the Apps page of your Zapier account and click + Add connection. You need an Adrapid account, plus access to any template you did not create yourself.
- 02
Choose Adrapid
Type Adrapid in the dialog's search box, select it among the results, then click Add connection. A new browser tab opens on the Adrapid side. Keep it open.
- 03
Sign in and allow
Log in to Adrapid in that tab and grant Zapier access to the account. The connection then appears in your list, ready for every Zap you build. No second login.
Your first Zap: an email to the client for every finished banner
GoalEach banner Adrapid finishes triggers an email to the client contact, asking for approval.
- 01
Set the trigger
Create a Zap, pick Adrapid as the app that starts it and
Banner Readyas the event, then select the Adrapid connection added earlier. - 02
Test on a real banner
Run the trigger test. Zapier brings back the three most recent banners of the account, so finish one in Adrapid first if none exists yet.
- 03
Add the email step
Add Gmail as the next step, enter the client's address, and map the banner details sent back by Adrapid into the subject and the body.
- 04
Test, then publish
Test the Gmail step and read the email that arrives. Then click Publish. Each email sent costs one task; the trigger costs none.
Adrapid trigger on Zapier
1 event starts a Zap when something happens in Adrapid. Zapier checks for them at the interval your plan allows.
Banner Ready
Polling triggerIn Zapier“Triggers when a new banner is ready.”
Starts a Zap once Adrapid has finished producing a banner, which is the right moment to send it somewhere: a client, a shared folder, a review channel. It is the event Zapier highlights for Adrapid, and the natural partner of Create Banner when another Zap does the creating.
Adrapid actions on Zapier
Adrapid gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Banner
ActionIn Zapier“Creates a banner from some data. It can be an animated html5, image or video.”
Produces a banner from the data your Zap passes in, as an animated HTML5 file, a still image or a video. You choose the Template and the Formats; the rest is mapped from earlier steps.
Get Banner
ActionIn Zapier“Get banner. Used after a create Banner action with a delay to make sure the banner is ready.”
Retrieves one banner by its Banner Id, usually the ID that Create Banner returned a step earlier. It is meant to run after a pause, once rendering is done.
When it breaks
Zapier attaches no help article to Adrapid, so the known failure points are the general ones of every Zap, plus the required fields.
Most of these do not raise a loud error. They show as banners that never arrive, or a task count that drops too fast. The Zapier troubleshooting guide covers the first checks.
Older banners never trigger
A Zap reacts only to what happens after it is switched on. Banners finished before you clicked Publish are never sent through Banner Ready.A Zap that keeps restarting
If a Zap started by Banner Ready also runs Create Banner, each new banner can start it again, and the task count drains fast.A large batch gets held
When many banners finish at once, after a bulk run, Zapier's flood protection can hold the trigger back before the Zap goes on.No duplicate runs on polling
Zapier remembers which banners Banner Ready has already returned, so the same banner does not start the Zap a second time.
Need help automating Adrapid with Zapier?
A person reads every message.



