Skip to main content
There are six ways to build the same thing on Bolna. They all produce an agent that can place and receive phone calls, and you can switch between them later — an agent created in the dashboard is fully editable over the API, and the reverse is also true. Pick the row that matches how you work.

​
How to decide

Start in the dashboard if you are evaluating

Agent Studio gets you to a real call fastest, and everything it produces is visible and editable in the agent builder.

Start with the API if calls are triggered by your systems

Anything you can do in the dashboard is available over the API, including creating agents, placing calls, and pulling transcripts.

Choose a graph agent when the flow is strict

Use it when the conversation must follow defined states — verification, eligibility checks, scripted collections. See Graph agents vs workflows.

Choose a no-code tool when the trigger lives elsewhere

If the call should fire from a spreadsheet or CRM event, use Make.com, n8n, Zapier, viaSocket or Google Sheets instead of writing a backend.
These are not exclusive. A common pattern is building and tuning the agent in the dashboard, then triggering calls in production over the Make call API or in bulk with batches.

​
What every path still needs

Whichever route you take, you will need a phone number and a telephony provider before real calls work. Bolna can sell you a number, or you can bring your own Twilio, Plivo, Exotel or Vobiz account, or your own SIP trunk — see Choose a telephony setup.

​
Next steps

Build your first agent

No code, in the dashboard

Make your first call

Four API calls end to end

What it costs

Pricing in one screen