--- title: "JustCall Integration" description: "Give agents your JustCall cloud phone system. They log call notes and dispositions, send and reply to SMS and MMS, poll for inbound text replies, sync contacts, and report on calls and texts by agent, number, or date range." url: https://flowrunner.ai/integrations/justcall date_modified: 2026-08-04T10:04:16-07:00 --- # JustCall [Messaging](https://flowrunner.ai/integrations/category/communication-messaging) Give agents your JustCall cloud phone system. They log call notes and dispositions, send and reply to SMS and MMS, poll for inbound text replies, sync contacts, and report on calls and texts by agent, number, or date range. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 17 actions · API key · available [JustCall website](https://justcall.io/) · [Platform Documentation](https://developer.justcall.io/) · Capability data verified 2026-07-27 1. The afternoon sweep pulls the day's completed conversations through List Calls 2. Get Call retrieves each call's duration, agent, recording URL, and whatever notes the rep managed to leave 3. Calls with no disposition get matched to their CRM records so the outcome can be reconstructed 4. Add Call Notes and Disposition logs the outcome code and a summary on every call the reps left bare 5. Prospects who asked to be followed up by text queue with a drafted message and the conversation context 6. The rep approves each first-touch text before it sends from the team's number 7. Send SMS delivers the approved follow-ups from the right JustCall number 8. When Check Text Reply detects a response, the rep gets pinged in the channel with the thread attached ## What This Integration Enables The phone system already knows what your team actually did today: who they called, how long they talked, what they texted, and what came back. JustCall holds that record, and most teams let it rot unlogged. FlowRunner agents work the record while the reps work the phones: they annotate calls with notes and dispositions, send and track SMS and MMS from the team's numbers, keep the contact book synced with the CRM, and turn call and text history into reporting nobody has to assemble. - Post-call hygiene: outcomes and notes logged the same day, matched to CRM records, with recordings linked - Conversational SMS: outbound texts, threaded replies, and reply detection wired into follow-up sequences - Contact sync: the JustCall address book and the CRM agreeing on names, numbers, and companies - Activity intelligence: calls and texts filtered by agent, number, and date range, delivered as reports The division of labor is the point. Humans hold the conversations, which is the part that actually sells. Agents hold the record-keeping, and the messages that reach a customer's phone pass through a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) gate on the way. ### Without FlowRunner **Call logging loses to the next call**: Reps dial the next number instead of writing notes, and the pipeline report is built on blanks **Texts live and die in one phone**: SMS follow-ups happen from whoever's screen the conversation is on, invisible to everyone else **Activity reporting is a manual export**: Who called whom, how often, and what happened requires someone to assemble it ### With FlowRunner **Every call carries its outcome**: Agents backfill notes and dispositions the same afternoon, so the CRM reflects what actually happened **Texts are drafted, approved, tracked**: Follow-ups queue with context, send on approval, and replies surface to the right rep automatically **The activity report writes itself**: Calls and texts by agent, number, and day flow to the reporting sheet on schedule ## Use Case Scenarios ### The disposition backlog that stops existing By 4 pm, the day's calls include a dozen with no notes and no disposition. The sweep runs List Calls for the day, pulls Get Call for each bare record, and matches the number against [HubSpot](https://flowrunner.ai/integrations/hubspot) to reconstruct the context. Add Call Notes and Disposition writes the outcome code and a summary, and the CRM activity timeline gets the recording URL. The Monday pipeline review runs on complete data, and no rep spent Friday evening doing data entry as penance. ### SMS follow-up that behaves like a channel, not a side effect A prospect ends a call with "text me the details." The agent drafts the message with the pricing link and the rep's name, and the rep approves it from the queue. Send SMS delivers it from the same JustCall number the prospect just spoke to, and Check Text Reply polls the thread. When the reply lands, the rep gets pinged in [Slack](https://flowrunner.ai/integrations/slack) with the full exchange, and Reply to Text carries the conversation forward without anyone hunting for which number it lives on. Texts stop being a private side channel and become pipeline activity the whole team can see. ### A contact book that matches the CRM by morning New leads created in the CRM flow to Create Contact so reps see a name instead of a bare number when the phone rings. Nightly, the agent walks List Contacts against the CRM: numbers normalized to E.164, emails and companies filled in through Update Contact, and true duplicates queued for review with their call history attached. A person confirms before any Delete Contact runs, because deletion is permanent even though the call history survives. Meanwhile the reporting pass appends the day's calls and texts by agent from List Users to [Google Sheets](https://flowrunner.ai/integrations/google-sheets), and the activity report nobody wanted to build is simply there. ## Human-in-Loop Highlight Send SMS drops a message into a customer's pocket from your business number, and there is no unsend. One bad merge field, one stale list, one message sent at the wrong hour, and it is your team's primary line, the one attached to every active deal, that gets marked as spam or reported for compliance. Carrier filtering does not distinguish between a typo and a campaign. So first-touch outbound texts in FlowRunner queue for the rep who owns the relationship: the agent drafts the message with full conversation context, names the sending number from List Phone Numbers, and waits. Replies inside an existing thread flow more freely because the customer opened the channel, but the first message from a number to a person is a human decision. Delete Contact sits behind the same gate for a simpler reason: it cannot be undone, and the agent's duplicate match is a hypothesis until a person confirms it. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 17 actions ### Calls 4 - **List Calls** Retrieves calls filterable by type, contact number, JustCall number, agent, and date range, ordered by call time. The feed behind sweeps and reports. - **Get Call** Retrieves one call's full record: direction, duration, agent, recording URL, IVR data, notes, and disposition. - **Update Call** Updates a call's notes, disposition, and rating; only supplied fields change. - **Add Call Notes and Disposition** Logs a note and disposition code on a call in one step, the purpose-built action for post-call hygiene. ### Texts 5 - **List Texts** Retrieves SMS and MMS messages filterable by direction, contact number, JustCall number, and date range. - **Get Text** Retrieves one message's body, direction, delivery status, media attachments, and agent. - **Send SMS** Sends an outbound SMS or MMS from a JustCall number to a contact, both in E.164 format. The message that reaches a phone: the action this page's human gate exists for. - **Reply to Text** Sends a reply within an existing conversation, reusing the original thread's numbers automatically. - **Check Text Reply** Checks whether a contact replied to a previously sent SMS and returns the reply when one exists. The polling primitive behind follow-up automations. ### Contacts 5 - **List Contacts** Retrieves address book contacts with search across name, phone, and email. - **Get Contact** Retrieves one contact's numbers, email, company, and notes. - **Create Contact** Creates a contact with a first name and E.164 phone number, plus optional email, company, and notes. - **Update Contact** Updates supplied fields on a contact, the enrichment step that keeps the book matching the CRM. - **Delete Contact** Permanently deletes a contact; call and message history for the number survives. Cannot be undone, so it runs on human confirmation. ### Phone Numbers 1 - **List Phone Numbers** Retrieves the account's provisioned numbers with capabilities and owning agent, the source of every "from" number. ### Users 2 - **List Users** Retrieves the account's agents with role and availability, the keys for per-rep filtering and assignment. - **Get User** Retrieves one agent's profile, assigned numbers, and current availability. ## Frequently Asked Questions ### What can FlowRunner do with JustCall? FlowRunner agents can run List Calls, Get Call, and Update Call in JustCall, plus 14 more actions. ### Does connecting JustCall to FlowRunner require OAuth? No. JustCall connects to FlowRunner with an API key, no OAuth flow required. ### Can JustCall trigger a FlowRunner workflow automatically? JustCall doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at JustCall?** This integration exposes JustCall to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/justcall. Site index: https://flowrunner.ai/llms.txt