Automation integration
AgendaForge + Make
Wire AgendaForge into Make scenarios with your API key — webhooks in, contacts and sessions out.
AgendaForge connects to Make through its public REST API and REST-Hook webhooks, authenticated with an afk_live_ API key — so a Make scenario can listen for event activity and write records back into your directory. It is the same mechanism that powers our Zapier support: webhook events become your triggers, and a Create Contact action (it can also create sessions and sponsors) lets a scenario push data the other way. When a speaker confirms, a submission lands, or a sponsor changes, AgendaForge fires the matching webhook, your Make scenario catches the cue, and the data goes wherever your stack lives — a spreadsheet, a CRM, a Slack DM, a project board. This is real and documented, not a roadmap promise. One honest caveat up front: it is API and webhook based, not a one-click published Make app, so you connect by pasting your API key rather than clicking a logo in Make's app directory.
Capabilities
What the Make integration does.
- Fires REST-Hook webhook events to Make whenever something meaningful happens in your event, so a scenario can react in real time.
- Subscribes and unsubscribes Make scenarios to those triggers through the public REST API, authenticated with an afk_live_ key.
- Writes data back into AgendaForge from a scenario — the Create Contact action also supports creating sessions and sponsors.
- Connects with the same mechanism as the Zapier integration, so anything you can model in one you can model in the other.
Triggers
What fires, and what happens.
contact.added / updated / removed
Fires a webhook when a contact — speaker, sponsor contact, or registrant — is created, edited, or removed, so a scenario can sync it onward.
sponsor & session events
Fires when sponsors or sessions change, letting a scenario mirror your agenda or sponsor roster into another system.
speaker, submission, review & event lifecycle events
Fires for speaker confirmed/declined, submission created and status changes, review completed, and event published — the lifecycle moments worth automating.
Setup
Connect it in minutes.
-
Create an API key
In your event's API settings, generate a key beginning with afk_live_. This authenticates every webhook subscription and API call Make makes on your behalf, so keep it secret and rotate it if exposed.
-
Subscribe your Make scenario to a trigger
Using an HTTP or webhook module in Make, register a REST-Hook against the event you care about — contact, session, sponsor, or a lifecycle event. AgendaForge then posts to your scenario's URL whenever that event fires.
-
Add a Create Contact action to write back
To push data into AgendaForge, point a Make HTTP module at the Create Contact endpoint (it also creates sessions and sponsors) with your afk_live_ key. The full request shape is documented at /docs/api.
Good to know
This is an API and webhook integration, not a published one-click Make app in Make's directory. You connect by pasting your afk_live_ API key into HTTP or webhook modules and following the REST-Hook setup in /docs/api — there is no logo to click and no managed OAuth handshake. It is exactly the same mechanism behind our Zapier support; the upside is full control, the trade-off is a little manual wiring up front.
Questions
Make, answered.
Q.01 Is there a published AgendaForge app in Make's directory?
Q.02 What can trigger a Make scenario from AgendaForge?
Q.03 Can a Make scenario write data back into AgendaForge?
Q.04 How is this different from the Zapier integration?
Integration reviewed July 2026. See the API reference for webhook and Zapier details.
More integrations
Run your event with Make wired in.
Invite-only while we onboard early partners. Tell us about your event and we'll bring you in — white-glove, no training course required.