Limited Release

This action is in limited release and is not generally available.

Perform an HTTP Request

The Perform an HTTP Request action calls external APIs and webhooks, then stores the response for later workflow steps.

When to Use This Action

• You need to call a REST endpoint that does not have a dedicated workflow action
• You want to send a GET, POST, PUT, or DELETE request
• You need to send request headers, query parameters, or a POST/PUT body

Configuration

Personality / Credential / Call

Field	Description
API Personality	Optional. Select a personality to preconfigure authentication and base URL.
Credential	Credential used by the selected API Personality. Custom paths require an explicitly selected credential that belongs to your organization and matches the personality.
API Method	Optional predefined method from the selected personality.
Path	Custom path appended to the personality base URL when no API Method is selected.
HTTP Method	The request method: GET, POST, PUT, or DELETE.
Accepts	Accept header value used for the request.
URL	Full https:// URL for direct-call mode (when no API Personality is selected).

Inputs

Field	Description
Method Parameters	Dynamic parameters for a selected API Method.
Querystring Properties	Key/value pairs added to the URL query string.
Request Headers	Custom HTTP headers sent with the request.
POST Body Type	For POST requests only. Choose JSON or FORM encoding.
POST Body Fields	For POST requests only. Key/value pairs used as JSON properties or FORM fields.
PUT Body Type	For PUT requests only. Choose JSON or FORM encoding.
PUT Body Fields	For PUT requests only. Key/value pairs used as JSON properties or FORM fields.

Result Handling

Field	Description
Response Format	Choose how the response is stored: decoded body, raw body string, or full response object.
Error Handling	Choose what the workflow should do when the remote service returns an error.

Outbound Request Safety

• Direct-call URLs must use HTTPS and resolve only to public internet addresses.
• Custom personality paths must remain relative to the personality's configured API host.
• The action rejects private, local, reserved, malformed, unresolved, and mixed public/private destinations.
• The action never follows redirects. It treats every redirect response as an unsuccessful request.
• Connection and temporary DNS failures use the existing retry limit. Each retry resolves, validates, and pins DNS again.

Example: JSON POST Body

Set these values:

• HTTP Method: POST
• POST Body Type: JSON
• POST Body Fields:
  • id => {{custom.foo}}
  • domain => {{email.from.address}}
  • notify => true

This sends a JSON body equivalent to:

{
  "id": "{{custom.foo}}",
  "domain": "{{email.from.address}}",
  "notify": "true"
}

Returned Variables

If you set Store the results in Variable, this action returns one of the following based on Response Format:

• Decoded response body object
• Raw response body string
• Full response object including status code, headers, and body

Availability

This action is currently limited release.