We use analytics to understand how visitors use the site. Session recordings are disabled by default and will only be enabled if you opt in.
S
Savena

Developer integration

Custom API + Savena

Call any HTTP API from a Savena workflow.

Last updated 2026-05-01

When there is no native integration for a system you use, Savena workflows can call any HTTP API directly. The custom API step is configured visually inside the workflow builder — set the method, URL, headers, and body using values from the conversation, and use the response in later steps. This works for internal services, niche SaaS tools, or any REST API that takes an outbound request.

What you can do

Outbound HTTP requests

Make GET, POST, PUT, PATCH, or DELETE requests to any URL from a workflow step.

Visual request builder

Configure headers, query params, and JSON body fields visually. Reference conversation, contact, or workflow variables anywhere in the request.

Use responses downstream

Parse the API response and use returned values in later workflow steps — replies, tags, routing decisions, or other API calls.

Authentication

Add static or dynamic auth headers (API keys, bearer tokens) to authenticate against your services.

Common use cases

  • Look up a customer in your internal database before replying.
  • Post a notification to a tool that does not have a native integration.
  • Call your own backend to check order status, account status, or feature flags.
  • Trigger a downstream system when a conversation is tagged.

How to set it up

  1. 1Open the workflow builder and add an "API request" step.
  2. 2Set the method, URL, headers, and body. Reference conversation variables where you need them.
  3. 3Test the step against a real conversation.
  4. 4Use the response in later steps via variables.

Frequently asked questions

Can external systems trigger Savena workflows?

Not directly through the custom API step — it is currently outbound only. To trigger workflows from external systems, use channel-based triggers (a new conversation, a tag added by another step, etc.).

Does it support authentication?

Yes. You can add static API keys or bearer tokens via headers, or build the auth header dynamically from workflow variables.

What happens if the API returns an error?

The workflow step records the error and you can branch on the response status code to handle failures gracefully — retry, fall back, or escalate to a human.

Is there a request rate limit?

Limits depend on your plan and protect against runaway loops. For typical workflow usage, the limits are not a constraint.

Try the Custom API integration in Savena

Included in every plan. 14-day free trial, no credit card required.

Start free trial