# HTTP Action Configure an HTTP Action

Source: https://userguide.qualytics.io/flows/actions/how-tos/workflow/configure-an-http-action/

Add an **HTTP Action** to a Flow to send timely updates or alerts directly to a specified server endpoint, with a choice of HTTP verb and authentication method.

> **Note: Permission Required**
>
> To edit and publish a Flow, you need the **Editor** team permission on every datastore it relates to. Admins are exempt. See [Flow Permissions](https://userguide.qualytics.io/flows/flow/deep-dive/permissions/) for details.

## Field reference

The **HTTP Action Settings** panel shows the following fields.

| Field | Required | Type | Description |
| --- | --- | --- | --- |
| **Action URL** | Yes | Text | The server endpoint for the HTTP request, including the protocol (http or https), domain, and path. |
| **Http Verb** | Yes | Option | The action performed on the endpoint. Defaults to **POST**: - **POST**: sends data to create something new. - **PUT**: updates or replaces a resource. - **GET**: retrieves data without modifications. |
| **Username** | No | Text | The username used for authentication, paired with the **Auth Type** and **Secret**. |
| **Auth Type** | Yes | Option | How requests are authenticated. The dropdown lists the values in lowercase and defaults to `bearer`: - `bearer`: a token in the request header. - `basic`: username and password sent with each request. - `digest`: a hashed combination of the username, password, and request details. |
| **Secret** | Yes | Text | The password or token used for authentication. Keep it confidential. |
| **Message** | Yes | Text | The notification message, carried inside the JSON payload with dynamic tokens resolved when the Flow runs (see [Message](https://userguide.qualytics.io/flows/actions/deep-dive/message/)). Plain text only, Markdown formatting is not supported. It already comes filled in with the trigger's default template, and the action cannot be saved with it empty. |

> **Info: How the credentials are sent**
>
> With `bearer`, the secret goes in the request header as `Authorization: Bearer <secret>`. With `basic` and `digest`, the **Username** and the secret are sent through the standard HTTP authentication schemes of the same name, so the endpoint challenges and verifies them as usual.

> **Tip: Reset to defaults**
>
> The **Reset to defaults**  button at the top of the settings panel restores the **Message** to the trigger's default, the **Http Verb** to **POST**, and the **Auth Type** to **Bearer**. The **Action URL**, **Username**, and **Secret** are left as you set them, because none of them has a default to return to.

## Steps

**Step 1**: Navigate to the Flows page by clicking **Flows**  on the left side panel.

**Step 2**: On the **Definitions** tab, click the Flow. On its canvas, click the dashed **Action** placeholder after the trigger, or the **+** handle at the bottom edge of a node.

**Step 3**: In the **List of Actions** panel, pick the **Workflow** category, then click **HTTP Action**. The **HTTP Action Settings** panel opens on the right-hand side.

**Step 4**: Fill in the fields.

**Step 5**: Click **Test Workflow** to verify the Action URL. A confirmation message appears when the endpoint is reachable.

**Step 6**: Click **Save**. The node shows a **CHANGED** badge and the **You have unpublished changes** banner appears on the canvas.

**Step 7**: Click **Publish**  to make the action live.

*Last updated: October 15, 2026.*
