Any HTTP API, and email from your own domain

Workflows could already work with GitHub, Slack and PostgreSQL. Everything else meant either a public URL or waiting for us to build a connection for it. Today there are two new kinds of connection that cover a lot more ground.

Any HTTP API

An HTTP API connection holds a base URL and a key: Stripe, Notion, Airtable, HubSpot or one of your own services. Workflows get a get tool, and a request tool for POST, PUT, PATCH and DELETE once you tick Allow writes.

• The key stays on the connection. It's encrypted, sent the way the API expects (a bearer token, a named header, a query parameter or basic auth) and never appears in a definition or a run log.
• Requests stay under the base URL. A path can't name another host or climb out with .., and an optional allowed paths list keeps the connection to the part of the API you meant, such as /customers and /invoices.
• Form bodies too. Set form: true for APIs such as Stripe that take form-encoded requests.

Email

Add a Postmark, Resend, SendGrid or Mailgun connection with just an API key and a sender, and workflows get send_email: to, cc, bcc, subject, and a text body, an HTML body or both. The tool is the same whichever provider you pick, so switching providers doesn't change a workflow.

Give the connection an allowed recipients list, with addresses or whole domains such as @acme.com, and a workflow can only email the people you listed, however its model is prompted.

See Connections for setup.