> ## Documentation Index
> Fetch the complete documentation index at: https://phaseo.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Automation

> Use Phaseo from Zapier, n8n, Pipedream, and other automation platforms.

Phaseo works today in automation products that can send authenticated HTTP requests. Native marketplace apps can provide a more guided experience later.

## Shared request

Use these settings in an HTTP, webhook, or code action:

| Setting | Value                                    |
| ------- | ---------------------------------------- |
| Method  | `POST`                                   |
| URL     | `https://api.phaseo.app/v1/responses`    |
| Header  | `Authorization: Bearer <PHASEO_API_KEY>` |
| Header  | `Content-Type: application/json`         |

```json theme={null}
{
  "model": "openai/gpt-5-nano",
  "input": "Summarise the supplied workflow data in one paragraph."
}
```

Store the Phaseo API key in the platform's credential or secret store. Do not place it directly in a shared workflow definition.

## Zapier

Use **Webhooks by Zapier → Custom Request**:

1. Select `POST`.
2. Enter `https://api.phaseo.app/v1/responses`.
3. Add the bearer and content-type headers.
4. Map fields from earlier Zap steps into `input`.
5. Test the Zap with non-sensitive data.

A native Phaseo Zapier app would add model selection, structured-output actions, and Phaseo-specific authentication, but it requires publication through Zapier's developer platform.

## n8n

Use the **HTTP Request** node with bearer authentication and a JSON body. For structured workflow data, map the upstream item into the `input` field with an n8n expression.

A first-party n8n community node can later expose operations such as Generate Response, List Models, Get Model Pricing, and Create Embedding without manual HTTP setup.

## Pipedream

Use an HTTP request step or a Node.js code step. Store `PHASEO_API_KEY` as a Pipedream secret and read it from the step environment.

## Production guidance

* Set a spending limit on the Gateway API key used by each automation.
* Give each automation its own key so usage and revocation remain isolated.
* Use structured outputs when downstream steps expect machine-readable fields.
* Add retry handling for `429` and recoverable `5xx` responses.
* Avoid retrying non-idempotent external actions merely because a model step was retried.

## Related

* [Responses](../../api-reference/endpoint/responses.mdx)
* [Structured Outputs](../structured-outputs.mdx)
* [Error Handling](../../developers/error-handling.mdx)