Skip to main content
Events let your agent or app react to changes in external apps — a new contact created in HubSpot, a message posted in Slack, a file uploaded to Google Drive. Membrane subscribes to these changes and delivers them to your application. See External Events API Reference for the full API.

​
Subscribing to Events

Event subscriptions are created through Flows. A flow is a multi-step workflow triggered by an event — in the simplest form, it just sends a webhook to your app.
  1. Create a Flow in your Membrane workspace (via Console, CLI, or API).
  2. Set the trigger to an event type (see below).
  3. Add steps to process the event — the simplest setup is a single api-request-to-your-app node that sends the event data to your backend.

​
Event Types

​
App Events

Custom events defined by the connector — not tied to a specific data collection. Examples: form-submitted, payment-received, message-posted. Use a connector-event-trigger or app-event-trigger in your flow.

​
Data Collection Events

Triggered by changes to records in a specific data collection (contacts, deals, messages, etc.):
  • data-record-created — a new record appears in the external app
  • data-record-updated — an existing record changes
  • data-record-deleted — a record is removed
Use data-record-created-trigger, data-record-updated-trigger, or data-record-deleted-trigger in your flow.

​
Polling Intervals

For data collection events, Membrane detects changes via webhooks or polling. You can configure the polling interval:
  • Pull-based: default 300 seconds (5 minutes)
  • Full scan: default 10,800 seconds (3 hours)
Set these at the trigger node level or data source level. See Limits for minimum allowed intervals.

​
Logging

Membrane provides detailed logging for every step of the event pipeline: