> For the complete documentation index, see [llms.txt](https://docs.work-relay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.work-relay.com/processes/process-actions/process-actions-types/callout.md).

# Callout

### Generic Process Action properties

This action has generic properties, as other process actions:

* **Name** - give action a name in order to search for it easy, otherwise system will use ID of this Action.
* **Step** - the step action is added at. This property can't be edited manually, but it will be updated if move this action to other step or connector.
* **Type** - main property which determines what Action will do and it's configuration. Once action is created, type can't be changed.
* **Status** - you can activate or deactivate an action temporary (e.g., for debug).
* **Start Type** - can be set to "Before step" or "After step". 

{% hint style="info" %}
This option is available only when action is added to the step. If action is added to a connector, it will be executed like "After step", where step is the outgoing step of this connector.
{% endhint %}

* **Execute** - specify if Action will be executed always or when some conditions are matched.
* **Description** - used internally only for admin's goals.

### Overview

**Callout** action allows to create HTTP requests like GET, POST, PUT, and DELETE.

### Configuration

* Select necessary object in Context Object Type. 

{% hint style="info" %}
This is not mandatory, but can be useful - e.g., if you want to populate request parameters with field values based on another record shown in current form.
{% endhint %}

* Set **Action Type** = "Callout". 
* Select the request **Method**.
* Enter the endpoint **URL**.
* Check **Compressed** if you want to compress the data you send. If a response comes back in compressed format, it will be uncompressed and returned the uncompressed value.
* Check **Send as Blob**. It sets the contents of the body for the request using a BLOB.
* **Certificate Name** allows to add certificate name.
* Add **Headers**.
* Populate **Body** (in the text area).

<figure><img src="/spaces/kkIfnKKNSULyGZ085PIG/files/8EdXMn1X8GZ6uP67v2Ou" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
You can use Static values, Merge Fields or Formulas to populate Certificate Name, Headers and Body.

See more info on Merge Fields and Formulas at [Working with context objects](/automations/global-actions-and-action-groups/basics/working-with-context-objects.md) and [Working with functions](/automations/functions-and-formulas/introduction-and-usage.md).
{% endhint %}