- Home
- Resources
- Integrations
- Drimify
Drimify Zapier integrationAutomate Drimify with Zapier.
The Drimify Zapier integration has 1 trigger, 0 actions and 0 searches. It does one job: it notices each new play recorded in one of your Drimify games and hands it to another app, so a participant reaches your CRM or sheet without a manual export.
Verified Trustpilot reviews · AI, automation & growth agency
What the Drimify Zapier integration actually does
Drimify is a gamification platform: you build interactive games and put them in front of an audience. Hooked to Zapier, it becomes a starting point: each time someone plays, a Zap (the automation you build on Zapier, one trigger followed by one or more actions) picks up that play and passes it on to another tool you already use.
Three outcomes people usually build with Collect Your Application Data, the only operation on offer:
A lead in your CRM. Every play lands as a contact in HubSpot or a similar tool, so the sales team follows up on people who actually engaged with the campaign.
A running log. Each play adds a row to a spreadsheet, which gives marketing a list to sort and count without logging in to Drimify.
A team alert. A message goes to a chat channel when a play comes in, handy during a live event or a short promotion.
Now the honest part. Zapier cannot do anything inside Drimify. There is no action to create a game, change one or edit a participant, and no search to look one up. Data flows one way, out of Drimify. If a workflow needs to push something back in, this integration will not cover it.
The same app also has a page on the other side of the fence: the Drimify Make integration. If you are still weighing platforms, Make vs Zapier sets out the differences in general terms.
Zapier vocabulary in one minute
Seven words come back on this page. Here is what each one means in plain terms.
- 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 after it starts: the step that writes, sends or moves something for you in another app.
- Task
- The unit Zapier bills you for. One task equals one action your Zap finished successfully; your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer. It asks the app for recent items at a set interval and keeps only the ones it has not seen.
- Instant trigger
- A trigger the app reports by itself, calling Zapier the moment the event happens. Drimify does not offer one.
- Filter
- A step that lets the Zap continue only when the incoming item meets a condition you set, and stops it otherwise.
- Connection
- Your Drimify account linked to Zapier once, then reused by every step and every Zap that needs Drimify.
What it really costs
Drimify is not a premium app, so it works on the free plan. The bill depends on actions, never on the trigger.
- TriggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on Free
Watching Drimify for new plays costs nothing, however often Zapier checks. Each action that completes counts as one task; an action that fails is not counted. The free plan gives 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. Practical sum: plays per month times actions per Zap, against those 100 tasks.
Connect Drimify to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box. Before you start, make sure you have a Drimify account with at least one game set up.
- 02
Find Drimify and start the link
Type Drimify in the dialog, pick it from the results, then click Add connection. Zapier opens a new tab where Drimify asks you to sign in with the account that owns your games.
- 03
Sign in and grant access
Log in to Drimify and allow Zapier to reach the account. The connection then shows up on the Apps page, ready for any Zap. If a colleague owns the game, you need access to it before Zapier can read its plays.
Your first Zap: qualified players go to HubSpot
GoalEvery new play is checked, and only the ones you care about become HubSpot contacts.
- 01
Create the Zap and pick the trigger
Start a new Zap, choose Drimify as the app and Collect Your Application Data as the event. Select the Drimify connection you created a moment ago.
- 02
Choose the game to watch
Fill in the application type, then the application itself. Both boxes are required, and they decide which game feeds this Zap. One Zap watches one game.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent plays from that game, so you map later steps on a real one. No play yet? Play the game once yourself, then test again.
- 04
Add a filter
Click the plus icon, add Filter, and set three boxes: a value you spotted in the test result, a rule, and what to compare it with. Pick a text rule for text and a number rule for numbers.
- 05
Add the HubSpot action and map fields
Add HubSpot with Create Contact, connect your account, and drag the player details from the Drimify test into the matching HubSpot boxes. Test this step too and check the contact.
- 06
Publish
Click Publish to switch the Zap on. From then on, every new play goes through the filter. Keep in mind the filter makes it a multi-step Zap, so it runs on a paid plan.
The Drimify trigger
1 event starts a Zap when something happens in Drimify. Zapier checks for them at the interval your plan allows.
Collect Your Application Data
Polling triggerIn Zapier“Triggers when a new play has been recorded.”
Starts your Zap whenever a fresh play is recorded in the Drimify game you pick, and passes the details of that play to the next step. It is the single door between Drimify and the rest of your tools.
When it breaks
Zapier links no help article to Drimify, so the failures worth knowing come from how Zapier itself behaves.
Most surprises with this integration are about timing and history, not errors. Four cases to know before a campaign goes live.
Old plays never come through
A Zap only reacts to plays recorded after you publish it. Everything that happened before stays in Drimify, and moving that backlog is a separate job.Plays show up late
Drimify relies on a polling trigger. On the free plan, Zapier checks every 15 minutes, so a play can wait that long before your Zap sees it.A burst of plays gets held back
When a trigger suddenly returns a huge batch, Zapier's flood protection can hold it back instead of firing hundreds of runs at once.The Zap stops after the trigger
On the free plan a Zap has two steps. Add a filter or a second action and it needs a paid plan before it will run.
Need help automating Drimify with Zapier?
A person reads every message.



