- Home
- Resources
- Integrations
- Instamojo
Instamojo Zapier integrationAutomate Instamojo with Zapier.
The Instamojo Zapier integration listens to your payments and hands them to the rest of your tools. It offers 2 triggers, 0 actions and 0 searches: Zapier reads Instamojo, it never writes back. That one fact shapes every Zap you can build here.
Verified Trustpilot reviews · AI, automation & growth agency
What the Instamojo Zapier integration does for your payments
The integration is a one-way bridge. When a payment lands on Instamojo, or when a buyer walks away halfway, Zapier notices it on its next check and passes the details to another app you choose. Instamojo stays the source; everything else is where the information ends up.
Three results come up again and again. First, a clean sales log: New Successful Payment feeds a spreadsheet or an accounting tool, one line per paid order. Second, a recovery list: New Dropped-Off Payment collects the buyers who started paying and stopped, so someone can follow up while the intent is still warm. Third, a team alert: either trigger can post to a chat channel, so the person shipping the order hears about it without opening the Instamojo dashboard.
Now the part the app page skips. Zapier can't do anything inside Instamojo. There is no action to create a payment link, no action to refund, and no search to look up an older order. If the job is to change something in Instamojo, this integration is the wrong tool, and no setting will change that.
The other limit is timing. Both triggers are checked on a timer, never pushed, so a payment shows up in your other app after a delay that depends on your plan (more on that below). If you also weigh other platforms, the Instamojo Make integration page covers the same app on Make, and the Make vs Zapier comparison lays out the general trade-offs.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English, once.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event that starts the Zap. Here, a new payment on Instamojo, successful or dropped off. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: writing a row, sending a message, moving data. Instamojo has none, so actions come from other apps.
- Task
- The unit Zapier bills. One action that completes successfully counts as one task, and your plan is a monthly count of those.
- Polling vs instant
- A polling trigger is checked on a timer by Zapier. An instant one is reported by the app the moment it happens. Both Instamojo triggers poll.
- Filter
- A step that lets the Zap carry on only when the incoming payment meets a rule you set, and stops it otherwise. Adding one needs a paid plan.
- Connection
- Your Instamojo account linked to Zapier once, then reused by every Zap that needs it, so you never sign in twice.
What an Instamojo Zap really costs
Good news first: Instamojo is not a premium app, so it works on the free plan.
- Trigger checkFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps only
- Premium appNo
Watching Instamojo costs nothing. The trigger never uses a task, however often Zapier checks. What counts is each action that succeeds in the other app, one task per action; a failed action is not billed. The free plan gives 100 tasks a month and checks every 15 minutes, but it stops at two steps: one trigger, one action. Add a filter or a second action and the Zap needs a paid plan, even for one sale.
Connect your Instamojo account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an Instamojo account of your own, or access to the one whose payments the Zap should read.
- 02
Find Instamojo
Type the name in the dialog, pick Instamojo from the list, then click Add connection. Zapier then hands you over to Instamojo for the sign-in step itself.
- 03
Sign in and grant access
Log in to Instamojo in that tab and allow Zapier to reach the account. The connection then appears on your Apps page, ready for any Zap that starts with a payment.
Your first Zap: log every course sale and tell the team
GoalPicture a teacher who sells video courses through Instamojo and wants each paid order kept in a sheet for the accountant, with a heads-up in the team chat.
- 01
Build: pick the trigger
Create a Zap, choose Instamojo as the app and New Successful Payment as the event, then select the connection you made earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent payments of the account, so you map the next steps on a real order and see which values it carries.
- 03
Add the spreadsheet action
Choose Google Sheets and its row action, then drop the values the test brought back into the matching columns of the sheet the accountant reads.
- 04
Add the chat alert
Add a second action, Slack and its channel message, and reuse the same payment values in the text. This second action makes the Zap multi-step, so a paid plan is required.
- 05
Test, then publish
Run each step once and read what came back. When the new row in the sheet looks right, click Publish to switch the Zap on.
Instamojo triggers on Zapier
2 events start a Zap when something happens in Instamojo. Zapier checks for them at the interval your plan allows.
New Dropped-Off Payment
Polling triggerIn Zapier“Triggers when a new dropped-off payment is created.”
Spots buyers who started a payment on Instamojo and did not finish it. Each one becomes a fresh run of your Zap, with the details Instamojo recorded for that attempt, ready to send to an email tool or a CRM.
New Successful Payment
Polling triggerIn Zapier“Triggers when a new successful payment is created.”
Fires for each payment that goes through on Instamojo. This is the trigger behind most setups: a sales log, an invoice in your accounting tool, a welcome email for a new student, or a ping to whoever packs the parcel.
When an Instamojo Zap breaks
Zapier attaches no help article to Instamojo, so the problems you will meet are the general ones of a polling trigger.
None of them shows up as an error message. The Zap simply stays quiet, or arrives late, which is why each case below is worth knowing before a client asks where their order went. If a Zap misbehaves anyway, the Zapier troubleshooting page is the next stop.
Past payments never come through
The Zap only reacts to what happens after it is switched on. Orders taken last week stay in Instamojo; moving that backlog is a separate job, outside the Zap.A sale shows up late
Both triggers are checked on a timer. On the free plan a payment can wait up to 15 minutes before the Zap runs; Professional checks every 2 minutes.A big batch gets held back
If a trigger suddenly returns a huge pile of payments, after a migration for instance, Zapier's flood protection can hold the batch back instead of running it all.The second step is refused on the free plan
The free plan builds two-step Zaps only. A filter, or a second action such as a chat alert after the sheet row, turns the Zap multi-step and needs a paid plan.
Need help automating Instamojo with Zapier?
A person reads every message.



