Integrating Make into your AEvent campaign lets you push registrant activity into any of your Make scenarios in real time. When a registrant hits a moment on your timeline — registering, attending, missing the event, or clicking your offer — AEvent can automatically fire the Make scenario you choose, sending that registrant's data into the thousands of apps Make connects to. | Timeline Actions:  |
How to find your API info for Make
Unlike a paste-a-URL webhook tool, AEvent connects directly to the Make API and pulls your scenarios in for you. To connect, you will need three things from your Make account:
Your API Token
Your Environment URL (the zone your account runs on, for example us1.make.com)
Your Team ID
To find your API Token:
Log into your Make account.
Open your Profile, then go to the API / MCP access section and select API tokens. Create a token (give it scenario and hook read access) and copy it.
To find your Environment URL:
Look at your browser's address bar while logged into Make. The first part of the web address — for example us1.make.com or eu1.make.com — is your Environment URL.
To find your Team ID:
Open your Team settings in Make. Your Team ID is shown there (and also appears in the web address as the number after /team/).
You will enter the API Token, Environment URL, and Team ID into AEvent in the next section.
Adding Make to AEvent
To add your Make integration:
Navigate to Integrations within AEvent and click Add Integration.
In the panel, find and click Make to expand it.
Click Add Integration to open the connection window.
Enter your API Token, Environment URL, and Team ID from your Make account. (The Key (for Custom App) field is optional — leave it blank unless you are using a Make Custom App.)
Click Connect.
Once Make connects successfully, you will see its Connected status. Click Test to confirm the connection is working.
Configuring the Make Integration within a Campaign
Within any of your campaigns, open the Integrations tab to see all available integrations.
Find Make and activate it by toggling it on.
As long as you have activated the integration, you are ready to use it in your Timeline Actions. There are no required campaign-level settings for Make — you choose which scenario to fire on each individual timeline action.
Creating Make Timeline Actions
Trigger Webhook
What it does: Fires one of your Make scenarios for a registrant at the exact moment you choose on your timeline, passing that registrant's data into Make.
When to use it: Any time you want a registrant's milestone — registered, attended, no-showed, or clicked your offer — to kick off an automation in Make (add them to another tool, start a sequence, update a sheet, post to Slack, and so on).
To set up this action:
In your campaign's Timeline, click Create Action.
Choose when it should fire and who it applies to, then set the action to Trigger Webhook.
From the Select a Webhook dropdown, pick the Make scenario you want to fire. This list is pulled automatically from the scenarios in your connected Make team that have a Custom webhook trigger.
Click Create.
Note: If the Select a Webhook dropdown is empty, your Make team has no scenario with a Custom webhook trigger yet. Build a scenario in Make that starts with a Custom webhook module, then reconnect or refresh the integration in AEvent so the new scenario appears.
How to reconnect Make
If your Make connection stops working:
Navigate to Integrations in AEvent.
Find Make and click Test to check the connection.
If the test fails, click Re-Connect and re-enter your API Token, Environment URL, and Team ID.
Click Test again to confirm.
How to remove Make
To disconnect Make from AEvent:
Navigate to Integrations in AEvent.
Find Make and click the trash icon.
Confirm the removal when prompted.
Removing this integration will immediately affect
any campaigns that have a Make Trigger Webhook action active.
If you are experiencing issues, try Re-Connecting (above) before removing. You can always re-add the integration later.
Troubleshooting
"Test Connection" shows failed: Double-check your API Token, Environment URL, and Team ID. Make sure the Environment URL matches the zone in your Make address bar (for example us1.make.com) and that your API token has scenario and hook read access.
"Select a Webhook" dropdown is empty: Your connected Make team has no scenario with a Custom webhook trigger. Build one in Make, then reconnect the integration in AEvent so it pulls the new scenario.
Wrong scenarios listed: The integration lists scenarios from the Team matching your Team ID. If you expected different scenarios, confirm you used the correct Team ID.
Integration not appearing in a campaign: Check that your AEvent plan includes access to Make.
Timeline action not firing: Verify Make is toggled ON in the campaign's Integrations tab and that the connection shows Connected.
If you need any additional help connecting Make to AEvent, please don't hesitate to reach out to our support team!
Related Articles
Zapier — Connect AEvent to thousands of apps through Zapier webhooks.
Outbound Webhook — Send a raw webhook at registration or based on audience qualification.
Twilio — Add SMS and MMS timeline actions to your campaigns.