# HTTP Endpoint

Runs when an HTTP request is received and can return a workflow-defined HTTP response

## Plan availability

| Feature | Free | Starter | Pro | Enterprise |
| --- | --- | --- | --- | --- |
| Active workflows | 3 | 10 | 45 | Unlimited |

Allowances follow the [published Chatigram pricing page](https://chatigram.com/pricing/). Your organization’s Billing & Plans screen confirms its subscription and current usage. Plans can change. Plan information reviewed 2026-11-10.


## When to use this trigger

Runs when an HTTP request is received and can return a workflow-defined HTTP response

Choose this trigger when creating a workflow. A trigger determines which event starts a run; it is not a step you paste onto an existing branch.

## Configure the fields

| Field | What to enter |
| --- | --- |
| **Endpoint URL** | Send an HTTP request to this URL to run this workflow. Add an HTTP Response node for a custom response; otherwise the endpoint returns 204 No Content. |
| **Method** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **URL** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Header Name** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Header Value** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Authentication** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **cURL** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Require secret key** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Secret Key** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Generate secure random key** | Set this value in the inspector. Use the variable picker where the field supports expressions. |
| **Variable Extractors** | Define how to extract data from the request body. Extracted variables can be used in workflow steps and optional response nodes. |

## Use the result

Choose the output from the variable picker in a later step. Output names below identify the values supplied by this node; the picker inserts the correct reference for your node instance.

| Output | Meaning / label |
| --- | --- |
| `httpBody` | HTTP Body |
| `httpMethod` | HTTP Method |
| `httpQueryString` | HTTP Query String |
| `httpPath` | HTTP Path |

## Connect the next step

Connect the continuation shown on the canvas. Some nodes calculate their branches from the configured options. Read each branch label in the editor and connect the paths your workflow needs.

## Test it in a workflow

1. Configure this trigger with a small, recognizable test input or a test resource.
2. Check the variables from preceding steps and the connection selected in the inspector.
3. Save the workflow. For event-driven flows, generate the actual event; use **Run** only for a Manual workflow.
4. Open **Workflow Activity** and check the outcome before enabling wider use.

## If something goes wrong

- Check empty variables, selected resource IDs, and any fields that appeared after resource selection.
- Check the failed step in Workflow Activity before retrying. If the action may already have completed, inspect the destination first to avoid duplicates.
- Follow the [troubleshooting guide](/help/troubleshooting/) for a symptom-by-symptom checklist.

## Related guides

- [Work with variables](/workflows/variables/)
- [Understand branches and error handling](/workflows/branches/)
- [Browse all nodes](/reference/nodes/)
- [Chat Status Change](/nodes/conversation-status-change/)
- [Conversation Start](/nodes/conversation-start/)
- [Cron](/nodes/cron/)
- [Database Operation](/nodes/database-operation/)
- [Manual](/nodes/manual/)


## Catalog coverage

This is the currently documented selection. Chatigram continues to add nodes, triggers, App Connections, and integrations. Use each page’s review date and the current application selectors to check what is available now; this catalog is not a fixed limit on future features.