HTTP Response
Return an HTTP response from an HTTP Endpoint workflow
Plan availability #
| Feature | Free | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Active workflows | 3 | 10 | 45 | Unlimited |
Allowances follow the published Chatigram pricing page. 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 node #
Return an HTTP response from an HTTP Endpoint workflow
Add HTTP Response to a workflow branch using the node picker. Configure its fields in the inspector, then connect the next step.
This node needs conversation context. Use it in a conversation workflow; a Manual or scheduled trigger does not create a customer conversation by itself.
Configure the fields #
| Field | What to enter |
|---|---|
| JSON Type | Type of this JSON value |
| Property | JSON object property name |
| String Value | JSON string value |
| Number Value | JSON number value. Variables must resolve to a valid number. |
| Boolean Value | JSON boolean value |
| Status Code | HTTP status code returned by this workflow |
| Body Type | JSON responses use application/json. Custom responses can use any content type. |
| Content Type | Content-Type returned with the response body |
| JSON Body | Structured JSON returned by the response. String and number values can use variables. |
| Body | Response body. Use variables to insert workflow data. |
Use the result #
This definition has no fixed public output variables. It may perform an action, or expose dynamic outputs after you configure response extraction, a table, or another resource. Check the variable picker after configuring the node.
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 #
- Configure this node with a small, recognizable test input or a test resource.
- Check the variables from preceding steps and the connection selected in the inspector.
- Save the workflow. For event-driven flows, generate the actual event; use Run only for a Manual workflow.
- 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 for a symptom-by-symptom checklist.
Related guides #
- Work with variables
- Understand branches and error handling
- Browse all nodes
- A/B Testing
- Analyze Image
- Ask Multiple Choice Question
- ChatGPT Task
- Check condition
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.