Skip to main content
POST
Receive app events
The shared address that an app, such as a chat app, sends its events to. Every flow in your instance that listens to the app uses it. The plug of the app reads each event, names the answer the app expects and decides which flows get it.
No token is needed. Each flow checks every event against the signing key of the app, so a forged call starts no run. Keep the key in the Space variable APP_EVENT_SECRET_<APP>.
{app} is the short name of the plug, such as slack. The Trigger tab of a flow that listens to the app shows the full address.

Request

The body is what the app sends, up to 1 MB. The app’s own headers are handed to the plug, except credentials.

What happens

1

The plug reads the event

It names the event, the account it belongs to and the answer for the sender, for example a reply to an address check.
2

Flows are chosen

Flows that are switched on and listen to that event of that account are picked, up to 100 for one event.
3

Each flow checks the signature

The check uses the Space variable APP_EVENT_SECRET_<APP>, for example APP_EVENT_SECRET_SLACK. A flow whose variable is missing shows a trigger error and starts nothing. A flow whose check fails starts nothing.
4

Runs start

Each flow that accepts the event starts one run per item.

Answers

When the plug asked for an answer, the address sends exactly that, so the app’s address check passes. Otherwise:
Last modified on November 5, 2026