Fix broken ActiveCampaign tagging in Make (checklist)

Quick diagnosis (5 minutes)

1. Confirm the symptom
• Is the contact missing entirely in ActiveCampaign?
• Or the contact exists, but the tag is missing?
• Or the tag exists, but the automation that should fire on that tag didn’t start?

2. Check whether the Make scenario is ON and has recent runs
• In Make, open the scenario and confirm it’s toggled on.
• Open Scenario history and look for recent errors or “Scenario was turned off” events.

3. Verify Make connections (ActiveCampaign + Airtable)
• In Make, open Connections and check for “Reauthorize” / “expired” states.
• Reauthorize anything that looks suspicious, especially OAuth-based connections.

4. Confirm Airtable permissions + view filters
• If your scenario watches a specific Airtable view, confirm the view still includes the records you expect.
• Confirm the Airtable base permissions allow the Make connection user to read the table/view.

5. Confirm ActiveCampaign tag + trigger automation exists
• If the tag is new (ex: a newly introduced destination or segmentation label), Make might create the tag, but you still may need an ActiveCampaign automation that triggers on that tag.

Common ActiveCampaign + Make failure modes (and what to do)

1) Scenario is OFF (often due to verification failures)

• Records pile up in Airtable (or your “to process” view) but nothing happens.

• Make emails about “failed to verify connection” or “scenario turned off”.

• Turn the scenario back on.

• Reauthorize the failing connection (Airtable/ActiveCampaign/Gmail, etc.).

• In Make, add/confirm error handlers so individual bad bundles don’t stop the entire run.

2) Airtable permissions changed (or the scenario user lost access)

• Make errors about permission/authorization.

• The scenario may stop, or the Airtable module returns 0 bundles.

• Re-grant edit/read permissions to the integration user.

• Re-run the scenario after confirming the view/table is accessible.

3) Connection expired (OAuth) or needs reauthorization

• “Failed to verify connection” at the platform level.

• Modules won’t even reach their error-handling routes.

• Reauthorize the affected connection.

• If the failures correlate with outages, reauthorize and then monitor for reoccurrence.

4) Bad data bundle causes repeated failure → scenario deactivates

• One record with invalid data (ex: invalid email address) causes failures.

• After repeated errors, Make can deactivate the scenario.

• Add an error handler on the ActiveCampaign module (or wherever the bundle fails):
• Log the bad record
• Mark it as “needs manual review” in Airtable
• Continue processing remaining records

5) Tag created/applied, but the welcome series / automation never starts

• Tag exists on the contact, but no email series is sent.

• In ActiveCampaign, ensure an automation exists and is triggered by that tag.

• For new tags, create the corresponding automation manually.

Backlog recovery (replay / catch up)

1. Prevent re-sending to old/irrelevant contacts
• Add a filter in Airtable to only include active records (ex: exclude completed/cancelled stages).

2. Process in batches
• Run Make in smaller batches (ex: 10 at a time) until caught up.

3. Add a tracking field in Airtable
• Create a field like “AC tag added” (date+time).
• Update it from Make when the tag is successfully applied.
• Filter your “to process” view to only show records where AC tag added is empty.

Monitoring + prevention

• Create an email label/filter for critical Make errors (especially “scenario turned off” and connection verification failures).

• Review Make scenario history weekly for repeated errors.

• If Gmail is in the chain, watch for recurring OAuth expirations and plan a recurring reauth.

Get help with this