AB Tasty Zapier integrationAutomate AB Tasty with Zapier.
The AB Tasty Zapier integration gives you 6 triggers, 0 actions and 0 searches. Every one of them is instant, so test news leaves AB Tasty the moment it happens. It carries data out of AB Tasty to your other tools, never back in.
Verified Trustpilot reviews · AI, automation & growth agency
What the AB Tasty Zapier integration does for you
Zapier is a tool that links apps together without code. With AB Tasty, it listens for six kinds of events in your testing account (a campaign created, a status change, a learning created or changed, a sequential testing trigger, an SRM alert) and pushes each one to another tool you already use.
An SRM alert that reaches the right person. Hook SRM Trigger to a chat tool, and the analyst on duty sees the alert in the channel they already watch, instead of finding it a day later in the dashboard.
A launch log nobody has to keep by hand. With New Campaign and Change Status, a product manager gets one row per launch and one per pause in a spreadsheet, which is enough to answer "what was live last week?" without opening AB Tasty.
A knowledge base that fills itself. Learning Created and Learning Changed can copy every learning into a wiki, so the next team that plans a test reads what the last one recorded.
Now the limit. AB Tasty on Zapier has no action and no search: a Zap can't create a campaign, pause one, or look anything up in AB Tasty. The flow goes one way, out. If a plan needs the reverse direction, compare the options in Make vs Zapier before building anything, or ask a Zapier agency to scope it.
Zapier words in one minute
Seven terms come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build on Zapier: one trigger first, then one or more actions that run each time that trigger event shows up.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills. One task is one action that your Zap completes successfully, and your plan counts those.
- Instant vs polling trigger
- An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it there otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
What AB Tasty on Zapier really costs
AB Tasty is not a premium app on Zapier, so it works from the free plan.
- Free plan100 tasks a month
- Steps on the free plan2 (one trigger, one action)
- AB Tasty trigger0 task
- Premium appNo
The AB Tasty trigger itself never costs a task. You pay only when an action in another app completes, and a failed action is not counted. Two catches. The free plan stops at 100 tasks a month and at two steps per Zap, so a filter or a second action pushes you to a paid plan. The interval grid below concerns polling triggers only: all six AB Tasty triggers are instant, so they fire straight away on any plan.
Connect AB Tasty to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your AB Tasty account linked once, then reused by every Zap that needs it.
- 02
Find AB Tasty
Type AB Tasty in the search box of the dialog, pick it, then click Add connection. A new tab opens on the AB Tasty side, where the actual login happens.
- 03
Sign in and allow access
Log in to AB Tasty in that tab and grant Zapier access. You need an AB Tasty account, plus read access to any campaign data you don't own yourself and want a Zap to watch.
Your first Zap: SRM alerts in Slack, then a Jira ticket
GoalWhen AB Tasty raises an SRM alert, post it to the experimentation channel and open a ticket for the analyst who owns the test.
- 01
Create the Zap
Start a new Zap in Zapier. Pick AB Tasty as the app that starts the Zap, and
SRM Triggeras the event that starts everything. - 02
Choose the account
Select your AB Tasty connection, then the AB Tasty account to monitor. That second choice is required, and it decides which tests the Zap hears about.
- 03
Test the trigger
Run the trigger test. Zapier brings back the three most recent items from the account, so you map fields on a real alert rather than a blank.
- 04
Add Slack, then Jira
Add the Slack step, write the message, and map the alert details into it. Then add Jira and map the same details into the ticket. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test and publish
Run each step once and read what came back. When both look right, click Publish: the Zap is on, and each future alert costs two tasks.
The 6 AB Tasty triggers
6 events start a Zap when something happens in AB Tasty, and 6 of them are instant: the app calls Zapier straight away, whatever your plan.
Change Status
Instant triggerIn Zapier“Triggers when a campaign changes status.”
A campaign in your AB Tasty account moves to another status, and this one starts a Zap. Watch it when people outside the testing team need to know what is running right now, without logging in.
Learning Created
Instant triggerIn Zapier“Triggers when a Learning is created.”
Learnings are the notes your team records in AB Tasty. As soon as someone creates one, this trigger hands it to Zapier so it can travel to wherever your team keeps its notes.
Learning Changed
Instant triggerIn Zapier“Triggers when a Learning is changed.”
Edits matter as much as first drafts. Someone reworks a learning in AB Tasty, and Zapier receives the edited version, which keeps any copy of it elsewhere from going stale.
New Campaign
Instant triggerIn Zapier“Triggers when a new campaign is created.”
Fresh campaigns are what this trigger reports. Each time a campaign is created in the AB Tasty account you chose, the Zap runs once, which makes it the natural starting point for a launch log or a review queue.
Sequential Testing Trigger
Instant triggerIn Zapier“Triggers when a sequential testing is triggered.”
When AB Tasty flags a sequential testing event on your account, Zapier hears about it, so the people waiting on it don't have to keep checking AB Tasty.
SRM Trigger
Instant triggerIn Zapier“Triggers when SRM is triggered.”
SRM alerts are the kind of news nobody wants to discover a day late. This trigger forwards the alert to Zapier as soon as AB Tasty raises it, so it lands where someone will actually read it.
When the AB Tasty Zap breaks
Zapier lists no help article and no rate limit specific to AB Tasty. What breaks is the general behaviour of Zapier.
These four cases cover what goes wrong most often with an events-only app like this one. If a Zap still misbehaves after that, the Zapier troubleshooting guide walks through the next checks.
Past campaigns never show up
A Zap only reacts to what happens after you switch it on. Campaigns and learnings that already existed are not picked up, and moving that history is a separate job.A bulk change gets held back
If a large batch of events arrives at once, after an import or a migration for example, Zapier's flood protection can hold the batch back instead of running everything.The second step stops on a free plan
The free plan builds two-step Zaps only. Add a filter or a second action behind your AB Tasty trigger and the Zap needs a paid plan to run.The wrong account is watched
Each trigger listens to the AB Tasty account you picked when building it. Events from any other account in your organization never reach that Zap.
Need help automating AB Tasty with Zapier?
A person reads every message.
