Skip to main content
Connect your Bland account to bring your pathways and knowledge bases into Bluejay, edit pathways here, and send each Bland call to Bluejay.

Connect

1

Save the Bland keys

In Bluejay, open Settings → Integrations and choose the Bland tab. Save both keys:
  • API Key: Bluejay uses it to pull pathways and knowledge bases, place test calls, and push your edits back to Bland.
  • Webhook Secret: copy it from the General tab of your Bland organization settings. Without it, Bluejay rejects every call that Bland sends.
2

Sync the pathways

Click Sync Agents from Bland to create one agent for each pathway. To pick up changes you make in Bland, run the sync again or turn on Autosync from Bland, which syncs about every 5 minutes.
To add one pathway by hand, create an agent with the Bland connection type, and pick a synced pathway or paste its pathway ID.

What the sync pulls in

For each pathway, Bluejay pulls in:
  • The working copy of the pathway, with its nodes and routing. The pathway’s global prompt becomes the agent’s prompt.
  • The prompts and routing conditions of the Bland Persona that routes calls into the pathway, if there is one.
  • The pathways that it warm-transfers into, up to 4 levels deep and 8 pathways in total. A pathway that only one other pathway transfers into, and that no Persona routes calls into, gets no agent of its own. Its calls go to that pathway’s agent.
  • Its connection type. A pathway with a Bland web agent gets the WebSocket path, and a pathway without one gets the phone path.
The sync also copies every Bland knowledge base into a Bluejay knowledge base, so custom metrics can check answers against the same content. Bland does not say which pathway uses which knowledge base, so attach each one to its agents yourself. A later sync updates the same knowledge base in place. A sync never deletes an agent. If you delete a pathway in Bland, its agent stays in Bluejay.

Edit a pathway

1

Pull the working copy

On the synced agent’s Workflow tab, pull the working copy. A version you pull is read-only, so pull the working copy if you plan to push.
2

Edit and push

Push your edits back to the working copy. Bland cannot store routing changes in the working copy, so a push that changes routing goes out as a new version.
3

Publish

Publish a version to staging or production. Production gets a copy of the version with a new number. Staging keeps the number.
Bluejay opens a session with the pathway’s Bland web agent, so no phone number is necessary. Use this path to iterate on pathway logic.If the pathway has no web agent in Bland, create one there and sync again. Bluejay then switches the agent to this path.

Call settings and request data

To make phone tests behave like your production calls, open the agent’s Connection Settings and paste JSON into the Bland tile:
  • Call settings (Optional): the call parameters that you send to Bland in production. Keys you leave out keep the Bland default. Bluejay rejects unknown keys, and also these keys, which it sets itself:
    • phone_number
    • pathway_id
    • pathway_version
    • from
    • metadata
    • request_data
    • webhook
    • webhook_events
For the request_data that your pathway expects, set agent variables on the agent’s Simulation Settings tab. Before each call, Bluejay adds the Digital Human’s traits and the Send-call variables from its Digital Human card on top, and writes the Digital Human’s name, phone number, and email over matching keys.Bluejay sends call settings and request_data only on calls that Bland places. WebSocket and chat runs do not use them.

Troubleshooting

Last modified on November 16, 2026