Connect an integration

Use the Call an API node to look up or send data to your CRM, helpdesk or any web service during a call.

Updated October 28, 20263 min readFor owners and admins

A call flow can talk to other software while a call is going on. For example, it can look up the caller in your CRM, or tell your own system that a call came in. You do this with the Call an API node.

The node has two Source options:

  • Saved integration: an integration set up once on the Integrations page, with its login details stored safely. Use this for anything you'll use more than once, or that needs a password or key.
  • Ad-hoc HTTP request: a one-off request typed right on the node. Use this for a quick webhook or a public web address.

Setting up a saved integration is technical work. You may want your developer or IT person to do it. The Call an API node reference has the full details.

Who can set up integrations. Owners and admins, and anyone whose role lets them manage integrations.

1. Add the integration

Open Integrations (in the main menu).

  • If the service you use is already listed, open it.
  • Otherwise, click Import spec to bring one in from Templates, from an OpenAPI or Postman file, or from a curl command. You can also click New integration to build one from scratch.

A new integration starts as a draft. Open it and click Publish when it's ready to use in flows.

2. Add a connection

A connection holds your login details for the service, like an API key.

  1. Open the integration and go to the Connections tab.
  2. Click Add connection.
  3. Give it a name, like "Main CRM", and fill in the details the service asks for.
  4. Click Create connection.

Your login details are stored encrypted. They never show up in your flows or call logs. You can Rotate them later, or Disable or Delete the connection.

To check it works, open the Operations tab, pick an operation and click Run test.

3. Use it in a call flow

  1. Open your call flow and add a Call an API node.
  2. Set Source to Saved integration.
  3. Pick the Integration, the Operation and the Connection.
  4. Fill in the Inputs. You can use details from the call, like the caller's number.

For a one-off request, set Source to Ad-hoc HTTP request instead, and fill in the URL, Method, and if needed the Body (JSON) and Authentication.

4. Handle success and failure

Open Where the call goes next on the node and pick a step for each result:

  • When the request succeeds: it worked. Carry on.
  • Not found / client error (4xx), Server error (5xx), Times out or Can't connect: it didn't work. Play a short message or send the caller to a person.
  • Otherwise: anything you didn't route above.

Need something more specific, like one status code or a field in the response? Click + Add a rule. Later steps can check this one too: in a rule, pick From followed by that step's name, then succeeded, status code or error.

Always plan for failure. If the other service is down, your callers should still get through.

Common questions

  • I updated the integration but my flow didn't change. Flows keep using the version they were set up with, so a change can't break a live flow by surprise. Open the node and pick the new version.
  • The node can't reach my server. For safety, Hey Quad won't call private or internal network addresses. The service must be reachable on the public internet.
  • Where can I see what happened? Open the integration and go to the Runs tab.