HTTP requests and endpoints

Plan availability #

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.

Send an external API request #

Add External API integration. Configure the method, absolute URL, headers, query parameters, and body using the inspector. Keep query parameters in their own section. Follow the API provider’s documentation for the accepted input and authorization requirements.

The detailed External API integration guide explains methods, encoded query values, JSON bodies, complete-response and field extractors, array paths, and Success/Error handling with a worked order-lookup example.

Use HTTPS and a controlled test resource. Keep credentials out of shared examples. Where a protected connection or signed-request action fits your API, use it rather than distributing access keys in a copied workflow.

Extract a useful result #

Configure response extraction for the value you need. A whole response can be useful for inspection, while a JSON value extractor can provide a specific field for a later step.

Use the variable picker in the next node. If an extraction returns an empty value, check the actual response shape, whether an error response arrived instead, and the configured JSON path.

Create an HTTP Endpoint workflow #

Choose HTTP Endpoint as the trigger. Save the workflow to obtain the endpoint details shown in the inspector. Keep the request protection enabled unless your use case deliberately requires otherwise.

Copy the request example provided by your own application. Use placeholders in shared documentation and keep the actual secret private.

curl -X POST 'YOUR_WORKFLOW_ENDPOINT_URL' \
  -H 'Chatigram-Workflow-Trigger-Secret-Key: YOUR_SECRET' \
  -H 'Content-Type: application/json' \
  -d '{"message":"hello"}'

This example describes the request format; replace placeholders locally with the values from your saved workflow.

Return a response #

Add HTTP Response for a custom response and configure the supported status, headers, and body format. Without a custom response, a completed synchronous endpoint can return 204 No Content.

A workflow waiting for a ChatGPT Task can return 202 Accepted while the task is pending. Its later completion does not rewrite an HTTP response already sent. A workflow waiting for a customer message is also not a predictable synchronous API interaction.

Handle errors and retries #

Check connection permissions, request format, returned status, and response extraction. Do not assume a retry is harmless: the API may already have performed the action before the connection failed.

Use a stable request identifier when the destination supports duplicate prevention, and inspect the destination before repeating a write. See branches and fallbacks.