What Actions can't do yet

When you're done, you know what an Action can and can't do before you build on it.

Who this is for: anyone setting up Actions.

The editor lists the main points under How Actions differ from GPT Actions, at the bottom of 7. Actions.

Not supported

What	What you see
Anything that moves money (payments, charges, transfers, refunds)	"It moves money (payments, charges, transfers or refunds), which Actions don't do."
Swagger 2.0 schemas	"This is a Swagger 2.0 schema. Convert it to OpenAPI 3…"
Files uploaded in the chat (openaiFileIdRefs)	Required: the operation can't run. Optional: left out.
Uploading files to the API (multipart/form-data)	"The request body is sent as …, which isn't supported (JSON and URL-encoded forms are)."
Keys or values in cookies	"This API expects its key in a cookie, which isn't supported…"
OAuth without a visitor (client credentials)	"This API uses an OAuth flow other than the authorization code flow, which isn't supported…"
HEAD, OPTIONS and TRACE	"… operations aren't supported."
References to other files ($ref to another address)	"A parameter (or The request body) uses an outside reference (…), which Chirp Builder doesn't fetch."
Private or local addresses, and plain http	"That address points to a private network." / "That host name only works inside a private network." / "… must use https."

Money is spotted by words like pay, payment, charge, transfer, purchase, checkout, refund, payout, withdraw and buy in the name, path or summary of an operation that changes data. Operations that only read data are never blocked for this. It goes by the words, so check any operation that spends money under another name yourself.

Limits

• 10 Actions per Chirp, and 30 operations switched on across them. Only a schema's first 100 operations are read, and a schema can be up to 1 MB.
• 10 calls per reply, and 100 calls an hour to each Action from one network address (visitors on the same network share them), counted per clock hour. You and your team aren't limited when signed in.
• 20 seconds per call. Responses up to 1 MB, of which the AI reads the first 20,000 characters. A file in a response can't be read.
• Redirects are followed only to the same address, at most 3, and never for changes.
• Values the AI fills in: up to 2,000 characters each and 50 in a list. Inside a body, text up to 20,000 characters (or the schema's own limit) and lists up to 200; a body up to 100,000 characters.
• A confirmation waits 10 minutes, with up to 5 waiting per visitor, and one change per reply.
• The Chirp's AI model must be able to use tools: see What Actions are, and how they work.
• 60 tests an hour per person.
• Course tutors in the Academy don't use Actions.

Visitors signing in to their own accounts

Signing each visitor in to their own account at the service (OAuth) is coming soon. Until then, use Actions with an API key or no sign-in: see Add the API key an Action needs. A schema that uses OAuth is added without sign-in, with the note "This API signs each visitor in to their own account (OAuth), which is coming soon in Chirp Builder."