AFRUS Zapier integrationAutomate AFRUS with Zapier.
AFRUS Zapier integration: 8 triggers, 1 action, 0 searches. AFRUS is a CRM built around donations and leads. Zapier links it to your other tools without code, and all 8 triggers are instant, so even the free plan reacts the moment a gift lands.
Verified Trustpilot reviews · AI, automation & growth agency
What the AFRUS Zapier integration actually does
It turns AFRUS events into work done elsewhere. You build a Zap, which is a small automation on Zapier: one event in AFRUS (a donation succeeds, a lead registers, a subscription ends) starts it, then one or more steps run in other apps. It also works the other way, with a single action that drops new leads into AFRUS. No code involved, only menus.
Three results people usually set up first. A failed-payment alert: New Donation Failed pings whoever handles payments, so the failure gets a human reply instead of a silent loss. A gift ledger: New Unique Donation Success writes every one-off gift as a row in a shared spreadsheet that the board can read without an AFRUS login. A lead inlet: Create Lead takes sign-ups from a webinar form or a landing page and files them in your AFRUS organization, email included.
Now the part the app page skips. Zapier offers no search for AFRUS, so a Zap cannot look up an existing donor before acting. The only action creates a lead: nothing updates a record, logs a donation or closes a subscription from Zapier. And no Zap reaches back into past donations; it sees only what happens after you switch it on.
If those gaps matter, compare the platforms on criteria rather than reputation. The n8n vs Zapier and Make vs Zapier comparisons put the options side by side.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English.
- Zap
- Your automation on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it, here a donation, a lead or a cancellation.
- 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 equals one action your Zap completes successfully; your plan counts those.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling trigger is checked by Zapier on a timer. AFRUS only has instant ones.
- Filter
- A step that lets the Zap continue only when what arrived meets your condition, and stops it otherwise.
- Connection
- Your AFRUS account linked to Zapier once, then reused by every step in every Zap that touches AFRUS.
What an AFRUS Zap really costs
AFRUS is not a premium app, so it runs on the free plan. The bill depends on actions, never on triggers.
- Free plan100 tasks a month, unlimited two-step Zaps
- TriggerNever costs a task
- Failed actionNot counted
- AFRUS triggers8 instant, 0 polling
Watching AFRUS costs nothing: a donation that starts your Zap is free. Each action that succeeds counts as one task, and a failed one is not charged. A Zap with three actions burns three times faster than a one-action Zap. The free plan gives 100 tasks a month and unlimited Zaps, but only two steps per Zap: one trigger, one action. Add a second action, a filter or a search and you have a multi-step Zap, which needs a paid plan. The polling grid below does not touch AFRUS, since every trigger here is instant.
Connect AFRUS to Zapier in three steps
- 01
Open your Apps page
In Zapier, go to Apps and click + Add connection. A dialog opens with a search box. You need an AFRUS account first, plus access to anything you do not own and want the Zap to touch.
- 02
Find AFRUS and start the link
Type AFRUS in the search box, pick it from the list, then click Add connection. A new browser tab opens on the AFRUS side, where the actual sign-in happens.
- 03
Sign in and grant access
Log in to AFRUS in that tab and allow Zapier to use the account. The connection is then saved once and offered in every Zap you build, so the next AFRUS step skips this whole routine.
Your first Zap: catch failed donations
GoalWhen a donation fails in AFRUS, alert the payments channel and log the case in a sheet.
- 01
Create the Zap
Click to build a new Zap. Pick AFRUS as the app that starts it and New Donation Failed as the event, then choose the AFRUS connection you saved earlier.
- 02
Paste the Api Key
The trigger asks for your organization's Api Key. Paste the one from your AFRUS organization profile; without it, the step cannot be tested.
- 03
Test the trigger
Run the test. Zapier brings back the three most recent items from your account, so you map the next steps on a real failed donation rather than a blank template.
- 04
Add the two actions
Add the channel message, then the spreadsheet row, and map the fields from the trigger into each. Two actions make this a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each action once and read what came back. When both look right, click Publish. From then on, every new failed donation runs the Zap.
The 8 AFRUS triggers
8 events start a Zap when something happens in AFRUS, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.
New Lead Abandoned
Instant triggerIn Zapier“This event will be send every day at the 6:00 AM UTC with the leads abandoneds in the day before”
Hands your Zap the leads AFRUS flagged as abandoned, the people who came close and then dropped off. AFRUS groups them and sends them as one delivery covering the day before.
New Charge Recurrent
Instant triggerIn Zapier“Triggered when a new charge recurrent is success”
Fires each time a recurring charge goes through, which means a regular supporter's payment actually went through. That is the signal finance usually wants, rather than the original pledge.
New Donation Failed
Instant triggerIn Zapier“Triggered when a donation is failed”
Reports a donation that did not go through. Without an automation, these sit in AFRUS and nobody follows up with the donor.
New Lead Success
Instant triggerIn Zapier“triggered when a new lead is register success”
Starts when a lead registers successfully in AFRUS. It is the earliest moment you know a new contact exists, before any money moves.
New Recurrent Donation Success
Instant triggerIn Zapier“Triggered when a new recurrent donation is success”
Signals that a supporter has just set up a recurring donation. This is the commitment, the moment a one-time visitor becomes a regular giver.
New Unique Donation Success
Instant triggerIn Zapier“Thiggered when a new unique donation is success”
Catches every successful one-off gift, kept apart from recurring ones. Campaign reporting often needs exactly that split.
New Signature Project
Instant triggerIn Zapier“This event will be send every moment when a person make a sign a project”
Fires when someone signs one of your projects in AFRUS, the kind of signature a petition or pledge page collects. No money is involved, only a name joining a cause.
Subscription Canceled
Instant triggerIn Zapier“Triggered when a subscription is canceled”
Tells you a supporter ended their subscription. It is the clearest churn signal AFRUS sends, and the one most worth a human response.
The AFRUS action
AFRUS gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create Lead
ActionIn Zapier“Create a lead in your organization account”
Adds a new lead to your AFRUS organization from any other app, so contacts collected elsewhere land in the CRM without retyping.
When an AFRUS Zap breaks
Zapier attaches no help article to AFRUS, so the known traps are the general ones. They still bite.
Three cases cover most surprises. If a run fails and the reason is unclear, the Zapier troubleshooting guide walks through the usual suspects step by step.
No backfill of past donations
A Zap only reacts to what happens after you publish it. Gifts and leads already in AFRUS are not picked up; moving that history is a separate job.The Create Lead loop
New Lead Success plus Create Lead on the same account: each lead the Zap writes starts the Zap again, and the task count drains fast.Bursts held back
A sudden huge batch, after a bulk import or a viral appeal, can be held back by Zapier's flood protection instead of running straight through.
Need help automating AFRUS with Zapier?
A person reads every message.



