# External Integration

## HTTP Request

Calls an external REST API from within a workflow.

<figure><img src="/files/aObT563AcJxtz3tXHXrw" alt=""><figcaption></figcaption></figure>

| Field            | Description                                                                                 |
| ---------------- | ------------------------------------------------------------------------------------------- |
| **Method**       | GET, POST, PUT, PATCH, DELETE                                                               |
| **Endpoint URL** | Supports dynamic values: `https://api.example.com/orders/{$.body.id}`                       |
| **Request Body** | JSONPath to send a subset of the state (e.g., `$.body`). Leave empty to send the full state |
| **Credential**   | Select a saved credential for authentication                                                |

<figure><img src="/files/hue69HgDXyuBVHcOpVkL" alt=""><figcaption></figcaption></figure>

The next task in the workflow receives the HTTP response in this format:

```json
{
  "statusCode": 200,
  "body": { }
}
```

Use `$states.input.body.<field>` in a downstream JSONata task to extract response values.

{% hint style="info" %}
HTTP tasks require a saved credential. If none is selected, Wire Flow uses a fallback method. Credentials are managed in the Secrets Manager — accessible from the Workflow List page or from the HTTP task's Properties Panel.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.tillit.cloud/tillit/knowledge-base/setting-up-tillit/integrations/wire-flow/task-types-and-integrations/external-integration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.