Skip to content

Connect other systems: integrations, webhooks and API keys

See what can be connected, send events to partner systems with webhooks, and create or revoke keys for programs that read your data.

Checked against the screens:

Every organisation can choose its own words for the people and roles it works with. When you are signed in, this guide uses your organisation’s words. Otherwise it uses the product’s own.

For admins. These tools are mostly used with help from the platform team or a developer. Disconnecting removes the link, not your history.

Steps

  1. Open the Integration catalogue to see what can be connected and what is configured.
  2. For a bulk import, use the importer the card points to.
  3. For events, open Outbound webhooks and press New webhook. Give it a name, a web address and the events to send.
  4. Check Recent deliveries to see whether the partner received them. Use Test to send a sample.
  5. For a program that reads data, open API keys. Under Create a new key, name it and list its scopes. Press Mint key.
  6. Copy the new key at once and press Got it. It is shown only once.
  7. Use Revoke on any key under Existing keys that you no longer need. Use Edit or Delete on a webhook.

If it goes wrong

  • If a delivery keeps failing, it is retried up to ten times. Check the partner's address.
  • If you lost a key, revoke it and mint a new one. It cannot be shown again.
  • If a page cannot load, reload it and tell the platform team if it persists.

Integrations

The catalogue lists connections such as email and text sending, calendars, and file imports from other systems. Each is per organisation. Disconnecting deletes the link, not the data.

Webhooks

A webhook sends an event from your organisation to another system, such as Zapier or n8n. Each delivery is signed so the receiver can check it is genuine.

Failed deliveries are retried with longer gaps, up to ten times. Delete a webhook and any pending deliveries go with it.

API keys

A key lets a program read data you choose. Name it for its job. Limit its scopes to what it needs, such as reading people or reports.

We store only a hash, so a lost key cannot be recovered. Keep keys in a password safe and never in a message.

Requests are signed, and there is a limit of sixty a minute per key.

Keeping control

How it links together

Data sent by webhooks and read through keys comes from the same records people see. Every key and webhook change is in the audit log.

See the guides on the audit log, on single sign-on and on email delivery.

Sending data outAn event happens, a signed message goes to your partner, and you can check it arrived.
  1. Event happensSomething changes in Daymello
  2. Webhook sendsSigned with a secret
  3. Partner receives
  4. You checkRecent deliveries

Questions people ask

Can I see a key again?

No. It is shown once. Revoke it and make a new one.

What are scopes?

They limit what a key can read, such as people, sessions or reports.

Will a failed webhook be tried again?

Yes, with longer gaps, up to ten times.

Who can use these pages?

Admins. Some are normally used with the platform team.

Where is the technical guide to keys?

In the API quickstart guide.