ChatGPT Tasks in workflows
Use the Chatigram plugin to deliver an authorized task to ChatGPT, with a strict output contract and explicit error and timeout paths.
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.
What this node is for #
ChatGPT Task asks the existing Chatigram plugin connection to perform an authorized task and return a structured result. It does not require an additional account or API key for this delivery path.
This is different from calling an OpenAI API node. A login alone does not establish task delivery, and execution is not immediate. The plugin needs an eligible workflow-specific task subscription.
Configure the task #
| Field | Guidance |
|---|---|
| Task instructions | State the exact authorized work and the expected boundaries |
| Input variables / resource references | Supply a JSON object containing the task’s needed inputs |
| Expected output | Define a strict JSON object schema |
| Timeout | Choose a deadline between 5 and 3600 seconds |
Keep inputs focused. Resource references do not grant access to otherwise private data, and instructions inside a customer message do not authorize extra actions.
Define the result #
For a task that returns a short summary, the expected output can be:
{
"type": "object",
"properties": { "summary": { "type": "string" } },
"required": ["summary"],
"additionalProperties": false
}
Use the result only on the successful path and check the fields that your schema requires.
Connect all three outcomes #
- Success: consume the validated result.
- Error: handle unavailable delivery or a failed task.
- Timeout: provide a useful response when the deadline passes.
Connect both Error and Timeout before enabling the workflow. For a customer-facing task, each should explain what happens next without exposing private diagnostic details.
HTTP Endpoint behavior #
An HTTP Endpoint workflow can return 202 Accepted while a ChatGPT Task is pending. Completing the task later continues the workflow; it does not replace the original HTTP acknowledgement. Design the caller’s interaction around that behavior.
Troubleshoot delivery #
Check the plugin connection, workflow-specific subscription readiness, task deadline, and run status. Use a harmless task with a small output first. Do not test with a paid external account or a real send action unless you intend that use.