AgendaForge for n8n

Automate your event workflows with n8n. React the moment something changes in AgendaForge with instant triggers, and write records back with Create actions. This guide covers generating an API key plus the two ways to connect — pick whichever fits your setup.

Heads up: API keys are organization-wide and shared with Zapier and Make.com. A key you generate here works for all three integrations, and revoking it disconnects all of them.

Two ways to connect

• A. AgendaForge community node (recommended). Install the n8n-nodes-agendaforge node. It adds branded AgendaForge action nodes and an AgendaForge Trigger node. The trigger node auto-subscribes — when you activate the workflow it registers its webhook with AgendaForge for you (and unsubscribes on deactivation). No manual URL copying.
• B. Generic HTTP Request node (no install). Use n8n's built-in HTTP Request node to call AgendaForge Actions directly. This path covers actions only — for triggers use the community node (Path A), which auto-subscribes.

Both paths use the same API key and the same underlying endpoints.

1. Generate an API key

1. In AgendaForge, open Event Settings → Integrations → n8n.
2. Click Generate key, give it a recognizable name (e.g. n8n), and confirm.
3. Copy the key now — it's shown only once (it begins with afk_live_). Store it somewhere safe; you won't be able to view it again. If you lose it, revoke it and generate a new one.

You must be an organization Owner or Admin to create a key. You can revoke a key any time from the same panel.

2. The base URL

When n8n asks for the API base URL, use:

https://api.agendaforge.com/api/v1

This is the production public API host. If you are on a dedicated or self-hosted deployment, your admin will give you the correct host.

Path A — using the community node

1. Install n8n-nodes-agendaforge — on self-hosted n8n go to Settings → Community Nodes → Install and enter the package name; on n8n Cloud it appears in the node panel once verified.
2. Create an AgendaForge API credential: paste your afk_live_… key and leave Base URL as the default. It is validated against GET /me.
3. Actions — add the AgendaForge node, pick a resource (Contact / Session / Sponsor) and Create, then fill the fields. Records created this way are stamped source: "n8n".
4. Triggers — add the AgendaForge Trigger node, pick an event, and activate the workflow. The node registers its webhook with AgendaForge automatically and unsubscribes when you deactivate. No manual URL copying.

That's it — the field and event reference below (Path B) applies to the node too.

Path B — using generic nodes (no install)

Actions — write data into AgendaForge

Use n8n's HTTP Request node to create records. Authenticate with a Bearer header.

Example — Create Contact:

• Method: POST
• URL: https://api.agendaforge.com/api/v1/contacts
• Headers: Authorization: Bearer afk_live_…
• Body (JSON):

{
  "firstName": "Ada",
  "lastName": "Lovelace",
  "email": "ada@example.com",
  "company": "Analytical Engines"
}

Available actions:

Finding the Event ID: sessions and sponsors belong to a specific event. Map the eventId from an upstream AgendaForge trigger, or copy it from the event in the app. The Event ID must belong to the same organization as your API key — otherwise the action returns a permission error.

A record created via an action also fires the matching "added" trigger, so it can feed other workflows. You can confirm a key works with GET /me, which returns your organization name.

Triggers — use the community node

Triggers are handled by the community node (Path A): its AgendaForge Trigger node auto-subscribes when you activate the workflow. There is no in-app trigger panel.

If you can't install the node and need triggers with the generic Webhook node, you can subscribe manually by calling the API yourself — POST https://api.agendaforge.com/api/v1/hooks?source=n8n with { "event": "contact.added", "targetUrl": "<your n8n Webhook Production URL>" } and Authorization: Bearer afk_live_…, and unsubscribe with DELETE https://api.agendaforge.com/api/v1/hooks/:id. This is the advanced/manual equivalent of what the node does for you.

Available trigger events:

Deliveries are retried up to 3 times. Re-subscribing the same URL + event is a no-op (it won't create a duplicate).

Verifying the signature (optional)

Each delivery carries an X-Webhook-Signature header — an HMAC-SHA256 of the raw request body keyed with the endpoint's secret. To verify it in an n8n Code node:

const crypto = require("crypto");
const secret = "whsec_…"; // the endpoint secret
const body = JSON.stringify($json); // the raw delivered payload
const expected = crypto
  .createHmac("sha256", secret)
  .update(body)
  .digest("hex");
const received = $headers["x-webhook-signature"];
if (expected !== received) {
  throw new Error("Invalid webhook signature");
}
return items;

Security notes

• Keys are organization-wide and shared with Zapier and Make.com — anyone with the key can read and write your org's data through the public API.
• Keys are shown once at creation and stored hashed; AgendaForge can never display them again.
• Revoke a key from Event Settings → Integrations → n8n the moment it's no longer needed or may have leaked. Revoking takes effect immediately across n8n, Zapier, and Make.com.

Support

For help with the integration, contact hello@agendaforge.app.