Return a JSON response

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.

What this workflow does #

The HTTP Endpoint trigger accepts the configured request. HTTP Response returns status 200 and a small JSON object containing a message.

The example deliberately leaves the trigger secret empty and keeps request protection enabled. Set a fresh secret in the inspector before enabling the workflow; do not disable protection just to bypass the required setup.

Configure your endpoint #

Import the example, open the trigger, and generate or set your own secret. Save to obtain the endpoint URL. Keep the URL and secret private where appropriate for your use case.

Open respond to inspect the status and JSON body. The body is built with Chatigram’s structured JSON editor, so the downloadable definition contains the editor’s JSON-value structure rather than a raw string.

Test the result #

Enable the reviewed workflow and copy the request example shown in your own trigger inspector. Send the request with its required header and verify the response:

{
  "message": "Hello from Chatigram."
}

Check Workflow Activity as well as the caller’s response. If an error occurs, confirm that you used your own saved endpoint and current secret.

Extend the response #

Add response extraction to the trigger if you need request data as variables. Add your work before the response node and return only the fields the caller needs.

For waiting or long-running tasks, read HTTP request behavior before assuming the caller receives a synchronous final result.

{
  "format": "chatigram-workflow",
  "version": 1,
  "metadata": {
    "sourceName": "HTTP response starter",
    "importHelp": {
      "note": "Keep request protection enabled. Generate or set a fresh secret in the trigger inspector before enabling, save, and use your own endpoint URL and secret. The sample contains no usable credential."
    }
  },
  "workflow": {
    "instruction": null,
    "multiLanguageSupport": null,
    "properties": [],
    "trigger": {
      "$tag": "Trigger",
      "type": "HTTP_ENDPOINT",
      "data": {
        "secretKey": "",
        "authEnabled": true,
        "extractors": []
      }
    },
    "nodes": [
      {
        "$tag": "Node",
        "id": "d0c00000-0000-4000-8000-000000000001",
        "name": "respond",
        "parentId": null,
        "branchIndex": 0,
        "type": "HTTP_RESPONSE",
        "data": {
          "statusCode": 200,
          "headers": [],
          "body": {
            "$tag": "Json",
            "value": {
              "$tag": "Object",
              "properties": [
                {
                  "key": "message",
                  "value": {
                    "$tag": "String",
                    "value": [
                      {
                        "$tag": "Constant",
                        "value": "Hello from Chatigram."
                      }
                    ]
                  }
                }
              ]
            }
          }
        }
      }
    ],
    "gotos": []
  }
}