Integration Actions

Integration actions connect a rule to the outside world: call HTTP APIs, invoke marketplace extensions, and read or write durable storage.

At a glance

Action	Use it to
API	Make an outbound HTTP request and capture the response.
Extension	Invoke a published marketplace extension.
Extension Callback	Call back into the consuming project (extension authors only).
Storage	Save, retrieve, or delete a value in durable storage.

API (HTTP call)

The API action issues an outbound HTTP request. You configure the request URL (with optional URL segments), method, content type, body, and headers; the request content type can be none, plain text, JSON, XML, form url-encoded, or multipart form-data. OAuth 2.0 settings can be attached when the endpoint requires a token.

The response is mapped back into the context through these optional outputs:

Output	Captures
Response Content	The response body.
Response Status Code	The numeric HTTP status.
Response Is Success Status Code	Whether the status indicates success.
Response Reason Phrase	The status reason text.
Response Headers	Selected response header values.

A timeout (default 100 seconds) and a failure reaction control behavior when the call is slow or fails. The action can also be marked to continue asynchronously, so a long-running process resumes when your service calls back with a correlation id — see Webhooks & Callbacks. For authenticating inbound traffic to the engine, see API Access.

Extension

Invokes a published extension from the marketplace. You reference the extension by its id and version, then supply Inputs and bind its Outputs back into your context; variable maps and form inputs let you wire the extension's parameters to your own values. An optional exit rule set names where control returns.

Not allowed inside extensions Extensions cannot call other extensions, so the Extension action is unavailable inside extension projects.

Extension Callback

Used only by extension authors. It has nothing to configure: when the engine reaches it, the extension hands control back to the project that is consuming it, returning the declared outputs and resuming at the consumer's exit rule set. This action is valid only inside extension projects.

Storage

Reads and writes durable storage by key. The action takes a Storage Key and a Storage Action:

Storage Action	Behavior
Save	Writes the value at the given context key to storage.
Retrieve	Reads from storage into the given context key.
Delete	Removes the stored value (no context key needed).

The Storage action is not available inside extension projects.