- Introduction
- Getting started
- Build on any canvas
- Build with Case
- Reference
- Defining case keys (system vs. external)
- Establishing task I/O and write-back contracts
- Modeling primary and secondary stages
- Triggering a case from Data Fabric
- Implementing stage-level personas and permissions
- Setting SLAs and automated escalation rules
- Configuring a rework loop (re-entry)
- Configuring and testing the Case Manager Agent (preview)
- Build with Flow
- Delay
- Connector event
- HTTP Webhook
- Build with BPMN
- Operating
- Monitoring
- Optimizing
- Reference information
Connector event
The Connector event node, which pauses a running workflow until an event occurs in a connected app and then continues.
What it does
A Connector event node pauses a running workflow until an event occurs in a connected app, and then the workflow continues. It is listed in the Wait for event category of the Add node panel, under Connector event. The event comes through a connection to the app, the same kind that connector triggers use.
A Connector event node is not a start node. It has an input, and the workflow keeps its own trigger that starts it. A connector trigger, in contrast, starts the workflow when the event occurs.
When to use
- A running workflow must wait for an external event before it continues, for example after it sends an approval request and waits for the reply.
- Use a connector trigger instead when the event should start the workflow. Triggers describes the trigger types.
Configuration
Each connector event has its own name in the Add node panel, such as Email Received for Outlook. The properties panel has Parameters, Error handling, and Advanced tabs. The Parameters tab shows these fields, which can vary by event:
| Field | Required | Description |
|---|---|---|
| Connection | Yes | The connection to listen on. Refresh Schema reloads the event's fields. |
| Event fields, such as Email folder | Varies | Settings that scope the event. For Email Received, Email folder is required and selects the folder to watch. |
| Filter | No | Conditions that an event must meet to continue the workflow. Choose All (AND) or Any (OR), then select Add condition or Add group. With no conditions, every event continues the workflow. |
The panel also notes that the trigger is configured at the connection level and checks for events every 5 minutes. To change the interval, edit the connection, as Connector nodes describes.
Requirements
The node needs a working connection to the app. Connector nodes describes how to create one.
Next steps
- Triggers: the trigger types that start a workflow.
- Delay: pausing a workflow for a set time.
- Connector nodes: the connector actions available as nodes.
- Popular connectors: common apps, with a link to each connector.