Trigger Node
Send HTTP requests in real time and map response fields for downstream use.
Trigger nodes send an HTTP request when a user enters the node. Unlike composable destinations (which fire and advance immediately), trigger nodes wait for a successful HTTP response before the user continues to the next step.
Configure a trigger node
- Drag a Trigger node onto the canvas and connect it to the upstream path.
- Open the node settings and configure the HTTP request — URL, method, headers, and body template.
- Use event payload fields, synced profile fields, and custom attributes in your templates. Custom attributes are passed as
glca_<label>fields alongside event data.
Response fields
Map scalar values from the HTTP response to named labels for use downstream in the same event routing:
| Source pattern | Examples |
|---|---|
status_code | HTTP status code |
body | Raw response body |
payload.* | Nested JSON response fields (dot notation) |
headers.* | Response header values |
Supported value types: string, number, boolean. Objects and arrays are skipped.
Mapped response fields behave like custom attributes — they flow to downstream criteria, destinations, and later trigger nodes in the same message path.
Behavior
| Outcome | What happens |
|---|---|
| Successful response | Response fields are extracted, user advances to the next node |
| Failed or non-retriable error | User does not advance (routing stops for this message) |
| Retriable error | GrowthLoop retries the request |
Downstream use
Response field labels appear in:
- Destination node personalization and match field mappings
- Later trigger node request templates (as
glca_<label>)