Integrations

How to send events to your other tools with webhooks, make API keys, and check what was sent in the delivery log.

Before you start: only owners see Integrations. Staff don't have it in the sidebar. See Users, roles, and your account.

Webhooks

A webhook sends each event (a proposal sent, viewed, signed, declined, and so on) to a tool like n8n, Zapier, Make, or your CRM. Events are always recorded for your timeline and reports; webhooks decide where they're also sent.

You can have more than one endpoint, for example one for n8n and one for your CRM. Each has its own address, signing secret, switch, and choice of events. The top of the section says how many endpoints your plan includes.

Add an endpoint

Click Integrations in the sidebar.
Under Webhooks, click Add an endpoint.
Enter a Name (so you can tell your endpoints apart) and the Address your tool gave you.
Under Which events, choose Every event, including new kinds added later (not documents'), or Only the events ticked below and tick the ones you want. Events for agreements and consents sent on their own are listed separately under Documents, and an endpoint gets them only when they're ticked.
Click Add endpoint.
Copy the signing secret now. It's shown only once. Paste it into your tool so it can check each event really came from EngageCycle.

A new endpoint starts off, so nothing is sent until your tool is ready.

Turn it on and test it

On the endpoint, click Turn on. Tick Also send the last 7 days of events it would have had if you want recent events sent too, then click Turn on again.
Click Send test event. It reaches that endpoint, and only that one, within a minute.

To stop sending, click Turn off. Events are still recorded.

Change, replace the secret, or delete

Edit changes the name, address, or events. The secret and switch stay as they are.
New secret makes a new signing secret and shows it once. The old one stops working at once, so update your tool right after.
Delete stops sending to that address. Your events stay recorded.

Events you can receive

proposal.sent, proposal.viewed, proposal.booking_clicked, proposal.booked
proposal.signed, proposal.declined, proposal.expired
proposal.signer_signed, proposal.signer_declined (one of several signers signed or declined)
proposal.superseded, proposal.withdrawn, proposal.copy_viewed (a copied person opened their copy)
proposal.deadline_extended (you gave the client more time; the proposal's expires_at is then the new date)
link.requested
lead.created, lead.verified, lead.abandoned
lead.awaiting_review, lead.declined (offers that hold requests for your review; lead.declined is a request you declined or one that expired)
client.created (someone from an offer became your client: they signed, you added them, or you imported or added a client with their email)
Documents, only when ticked: document.sent, document.viewed, document.signed, document.declined, document.expired, document.withdrawn, document.superseded, document.signer_signed, document.signer_declined, document.deadline_extended
email.bounced, email.complained
webhook.test (from Send test event)

Each event carries a signature your tool checks with that endpoint's secret. A signed proposal's event includes a link to its PDF.

API keys

API keys let tools like n8n or Zapier work with your clients, catalog, and proposals: read them, add clients, send proposals, and download signed PDFs.

The API and MCP don't yet cover agreements and consents sent on their own, or walkthroughs. Send those from EngageCycle. Their events still go to your webhook endpoints, so a tool can act when one is signed.

Under API keys, enter a New key name, for example "n8n".
Under What the key can do, tick only what the tool needs.
Click Create key.
Copy the key now. It's shown once and can't be recovered.

The list shows each key's name, how it starts, what it can do, when it was created, and when it was last used. To stop a key working, click Revoke.

API reference under API keys lists every request a key can make.

MCP

MCP lets AI assistants that support the Model Context Protocol, like Claude and ChatGPT, look up clients and proposals, make drafts, and send them when you say so. MCP shows the server address, which API key to make, setup you can copy for each kind of assistant, and What it can do: each tool, whether it reads or changes data, and the key permission it needs. If your plan doesn't include MCP, the section says which plans do. See Use EngageCycle from Claude or ChatGPT.

Delivery log

The Delivery log shows the latest events and what happened at each endpoint: Delivered, Waiting, Retrying, or Couldn't send, with the number of tries and the last problem. An event that went nowhere says Not sent (no endpoint was on for it).

Click Full log for everything, newest first, and Show problems only to see just what's failing.
Click Resend to send a delivered or failed event to that endpoint again, from its first try.

If an endpoint fails three times in a row, owners get a notice. Failed events are tried again for up to 7 days.

If your plan stops including an endpoint (it allows fewer endpoints, or none), that endpoint's card says Deliveries are paused and owners get a notice. Its events wait until your plan includes it again. Upgrade, or turn the endpoint off.

For developers

Whoever builds your automation will want these pages. They're public and need no sign-in, so you can send them the links.

API reference: every request an API key can make, and an n8n example.
Webhooks: each event, an example of what's sent, and how to check the signature.
MCP: the MCP server's address, each tool, and the key permission it needs.

Good to know

An endpoint is sent events in order for each proposal, so a signed event never arrives before that proposal's sent event.
If your plan doesn't include a feature, Integrations says what it does and which plans include it instead of hiding it.
EngageCycle support can't change your endpoints, secrets, or API keys, even in a support session.