Re-entry is capped at ten
A start trigger set to run multiple times admits a contact at most ten times in twenty-four hours. A flow that looks broken is often just a contact that hit the cap, so we record it rather than leaving you to guess.
Integration · Twilio to ActiveCampaign
Twilio and ActiveCampaign integration
ActiveCampaign automations are good at deciding when someone should be called or texted. Twilio is what actually does it. We connect the two so the call or text happens, the result comes back to the contact, and a failure is something you hear about rather than a step that quietly did nothing. It is a one-time setup by our team, not a monthly middleware subscription.
- From $100, one-time setup
- No monthly fees from us
- Tested on your own calls before go-live
Twilio
ActiveCampaign
One call ends in Twilio. In ActiveCampaign:
- An automation reaches the stepContact meets your condition
- Twilio places the call or textFrom your own numbers
- Result written to the contactNote, tag or custom field
- One-time setup
- From $100
- Monthly fee from us
- $0
- Working days to a written scope
- 2
- Working days to build and test
- 5–10
Got it, thank you.
Check your inbox for a confirmation. We will reply within 2 working days with what we would do and what it would cost.
Two systems with very different ideas about failure
ActiveCampaign automations are forgiving by design. A contact enters, moves through, and the platform quietly protects you from loops: a start trigger set to run multiple times will re-admit a contact at most ten times in twenty-four hours, and a runs-once trigger will not re-admit someone who has already been through, even after you edit the conditions. Useful rules, and completely invisible when you are wondering why a contact did not get the call.
Twilio fails differently. It creates outbound calls through the API at one per second by default and queues the rest, so a burst becomes a delay rather than an error. And when your webhook does not answer properly it logs error 11200 and carries on. Put the two together without thinking and you get a flow where nobody is sure whether a contact was skipped by ActiveCampaign’s re-entry rule, delayed by Twilio’s pacing, or lost to a webhook that timed out. Most of this build is making those three outcomes tell you apart.
- Teams texting from automationsFollow-ups and reminders go out from your own Twilio numbers.
- Lead response flowsA new lead triggers a call attempt within minutes, with the result on the contact.
- Anyone who has lost messages in a flowSkipped, delayed and failed are three different things, and the contact record says which.
What we connect between Twilio and ActiveCampaign
A typical setup. We adjust each line to how your team uses Twilio and ActiveCampaign.
When this happensThis is what you get
An automation reaches a call or text stepTwilio places it from the number you choose
A text sent or receivedSaved on the ActiveCampaign contact, with the number used
A call outcomeA note, tag or custom field on the contact
A reply to a textWritten to the contact and able to start another automation
A webhook that failed with 11200Retried, then raised as an alert rather than dropped
A contact blocked by re-entry rulesLogged as skipped, so it is not mistaken for a failure
Field mapping, event by event
Each Twilio event and exactly what it writes in ActiveCampaign. Pick an event to see its fields.
1. Trigger · Twilio
When a call ends
Every call made or received in Twilio
2. Action · ActiveCampaign
Log the call note
In ActiveCampaign, on the contact — Where your team already works
ActiveCampaign field
Mapped from
What happens
Activity date
Date created15 Sep, 4:00 pm
Shown in your time zone
Date created15 Sep, 4:00 pm
Shown in your time zone
Call length
Call duration3 min 04 s
Stored the way ActiveCampaign expects
Call duration3 min 04 s
Stored the way ActiveCampaign expects
Direction
DirectionInbound
Inbound or outbound
DirectionInbound
Inbound or outbound
Recording
Recording urlPlayable audio
Added once the file is ready
Recording urlPlayable audio
Added once the file is ready
Call notes
Transcription textAsked for pricing
Saved as note text
Transcription textAsked for pricing
Saved as note text
Contact
Matched by phone number+1 415 555 0142
A new contact is created only if none match
Sample values are made up. The exact fields are agreed with you in your scope.
A one-time setup, not a monthly middleware bill
We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.
Web Repay integration setup
Middleware subscription
What you pay
One-time setup, from $100 (one-off)
A monthly plan, often priced by tasks or operations
As call volume grows
The same price, no per-task charges
Costs rise with every call that syncs
Who builds and tests it
We do, on your own Twilio calls
Your team builds and maintains every step
Where it runs
In your own Twilio and ActiveCampaign accounts, documented
Inside the middleware vendor’s platform
When something changes
Additional support as needed, when you request it
Your team fixes the broken steps
Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.
Where Twilio and ActiveCampaign setups usually go wrong
Runs-once does not reopen
Editing a runs-once trigger does not re-admit contacts who already entered, even if they now meet the new conditions. We flag where a change will not do what it looks like it should.
Error 11200 loses steps silently
Twilio logs 11200 when your webhook errors, times out or cannot be parsed, then moves on. We retry and then tell someone the same day.
One call per second, by default
Outbound API calls run at one per second unless your limit is raised, with the excess queued. A campaign that fires five hundred at once becomes a long tail, so we pace deliberately instead of letting it surprise you.
How we set it up
- 1
Agree what connects
Which automations trigger calls or texts, from which numbers, what is written back, and where failures should be raised. You get a written scope with a fixed one-time price.
- 2
Access for the setup
An ActiveCampaign user group with the permissions the work needs, and Twilio credentials you can revoke without touching your main login.
- 3
We connect and test
We run contacts through each automation, force a webhook failure on purpose, and check what sent, what was skipped by re-entry rules and what was alerted on.
- 4
Handover
A short document of what is connected, including the failure alerts. It runs in your own accounts, with no monthly fee from us.
Test call passedEvery field in the table checked
LiveWatched for the first week
What it costs
From
$100 one-time setup
Starting price for connecting Twilio and ActiveCampaign, built and tested. Larger mappings get a fixed quote in writing before we start.
No monthly fee from us. Additional support is available as needed, whenever you request it.
Free download
The integration health check
10 checks to make sure your website, CRM and dialer really are passing information between them.
From the blog
Further reading
Integrations
How to log every call from your dialer in your CRM
Every call on the right contact, with the outcome, the rep and the recording, and nobody typing notes afterwards. What to connect, how to match callers, and what to test.
CRM
Why your CRM is full of duplicates, and how to stop new ones
Duplicates come in through forms, imports, integrations and manual entry. Here is how to clean up what is there, and close the doors so they do not come back.
Dialers
Why fewer people answer your calls: spam labels and caller ID
When answer rates drop, the cause is often a warning label on your caller ID. How US carriers check and label calls, and what you can do about it.
Questions about Twilio and ActiveCampaign
Can ActiveCampaign automations send texts through Twilio?
Yes. An automation step places the text from your own Twilio number, and both the message and any reply are saved on the contact.
Why did a contact not get the call?
Usually one of three reasons, and the point of this setup is telling them apart: ActiveCampaign’s re-entry cap of ten per trigger per twenty-four hours, Twilio queuing behind its calls-per-second limit, or a webhook that failed with error 11200.
Will editing a trigger re-admit old contacts?
Not for a runs-once trigger. Contacts who already entered stay out even if they meet the new conditions, which surprises people often enough that we flag it during the build.
Is there a monthly fee?
No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us. Your ActiveCampaign plan and Twilio usage are unchanged.
Rather talk it through?
Thirty minutes on how your team uses Twilio and ActiveCampaign. You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Deal updatedReply received
Call-back taskAssigned to the contact owner