800.com
Voice & TelephonyManage toll-free numbers, call tracking, messaging, and analytics on 800.com. Agents attribute inbound calls to the campaign that produced them and route the follow-up work.
What This Integration Enables
A toll-free number on 800.com is a measurement instrument. Point a distinct number at a campaign, a landing page or a partner, and every call that arrives on it carries an answer to the question marketing teams usually cannot answer at all: which spend produced this conversation. The connector exposes that as something an agent can act on rather than a dashboard someone visits.
Get Call Analytics does the aggregation, shaped by a target metric and a grouping dimension such as tracking number or tag, narrowable to answered or missed calls and to a first or last touch attribution model. List Calls By Callee goes the other direction and breaks one inbound call into the legs it produced, so a ring group that looks healthy in the summary reveals the destination that keeps timing out. Get Call Timeline reconstructs a single call step by step, through ringing, forwarding and voicemail, which is what you need when the question is why a specific lead was missed. Around that sit the address book for CRM sync, group and user lookups for routing follow-up work, webhook subscription management, and SMS and MMS from a messaging-enabled number. That last one is the part an agent never runs on its own, because every send costs money and reaches a real phone.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Crediting phone leads to the campaign that produced them
A deal appears in the CRM sourced from a phone call, which in most attribution setups is where the trail ends. An agent runs Get Call Analytics over the window before the deal was created, grouped by tracking number and filtered to answered calls, and matches the caller number on the deal to a tracking number. It then runs Get Call Timeline on that specific call to confirm the routing path and that the call reached a person rather than voicemail. The tracking number, the campaign attached to it and the answering destination all get written back to the deal, so the spend behind the conversation is credited without anyone exporting a report.
Finding the destination that keeps dropping calls
The inbound summary looks fine and the sales team says calls are not reaching them. On a nightly run the agent pulls List Calls By Callee for the previous day, which reports each leg of a ring group with its own status: answered, busy, rejected or timed out. Where one destination's legs are overwhelmingly timing out while others answer, the agent runs Get Call Timeline on a sample of those calls to reconstruct exactly how far each got, then posts the pattern to the operations channel with the specific number and the sample calls attached. The output is a named destination and evidence, not an aggregate that leaves someone guessing.
Address book in step with the CRM, suppression respected
An agent keeps the 800.com address book aligned with the CRM in both directions. New CRM records become Create Contact calls so inbound calls from those numbers resolve to a named person and show useful context on the screen pop. CRM edits become partial Update Contact writes rather than full record replacements. Coming the other way, List Contacts and Get Contact carry the unsubscribe flag, and the agent treats that flag as the authority: any messaging step reads it first, and a contact that has opted out is dropped from the audience before the audience is ever proposed to a person.
Human-in-Loop Highlight
Send Message is the one action on this connector that spends money and touches a customer in the same instant. It sends a real SMS or MMS from a messaging-enabled number, and once it leaves there is no recall. So an agent that has assembled a follow-up audience does not send it. It builds the list, runs List Group Contacts and checks the is_unsubscribed flag on every record, drops the opt-outs, runs List Numbers to confirm the intended sender is messaging-enabled, and then posts to the marketing owner in Slack with the whole proposal in one message: "Follow-up SMS ready for 218 contacts from the 24 hour missed-call segment. 31 opted-out contacts removed. Sending from the toll-free number ending 4120. Draft below. Approve to send." The agent waits. When the approval comes back it sends once, never inside a retry loop, and reports the result. This is human-in-the-loop where it earns its keep: the agent does the assembly and the suppression work that people get wrong, and a person owns the irreversible part.
Agent Capabilities
21 actionsCall Tracking and Analytics
4- List Calls Retrieves inbound and outbound call records with the caller and receiving numbers, duration, disposition and any logged outcome. Narrowable by date window, direction, status or outcome. Used to feed calls into a CRM or to build reporting.
- List Calls By Callee Retrieves call records grouped by the party that was rung, which is how ring groups and forwarding chains are reported. One inbound call produces several callee legs, each with its own status. Used to find the destination where calls are being dropped.
- Get Call Timeline Retrieves the ordered event timeline for one call, showing ringing, forwarding, voicemail and completion in sequence. Used to diagnose a missed call or reconstruct the routing path for a quality review.
- Get Call Analytics Retrieves aggregated analytics over a date range, shaped by target metric and grouping dimension such as tracking number or tag, and narrowable to answered or missed calls, to a minimum duration, and to a first or last touch attribution model. Used to attribute phone-sourced revenue without pulling every call record.
Numbers
1- List Numbers Retrieves the tracking and toll-free numbers on the company with line type, label and routing summary. Used to audit inventory or to confirm a valid sender before a message goes out.
Contacts
5- List Contacts Retrieves the company address book with number, name, email, postal address, notes, custom field and unsubscribe flag. Used to export for a CRM sync or to check opt-outs before messaging.
- Create Contact Adds a contact to the address book. Only the phone number is required. Used to push a new CRM record in so inbound calls from that number resolve to a known person.
- Get Contact Retrieves one contact by identifier with the full record including the unsubscribe flag. Used to enrich a call or message event with everything known about the other party.
- Update Contact Applies a partial update, changing only the fields supplied. Used to correct a single value after a CRM edit without resending the whole record.
- Delete Contact Permanently removes a contact from the address book. Calls and messages already recorded against the number are kept, but the number stops resolving to a named person. Cannot be undone.
Groups and Users
6- List Groups Retrieves the contact groups visible to the token across the account. Groups are the segmentation unit for the address book.
- List Company Groups Retrieves the groups belonging to the configured company, which is the set usable when segmenting that company's address book.
- List Group Contacts Retrieves every contact belonging to any group on the configured company, so a flow can build the full addressable audience in one pass. The unsubscribe flag is checked on each record before the list is used for messaging.
- List Users Retrieves the users visible to the token across the account with name, email and role. Used to resolve the person behind a user identifier on a call record.
- List Company Users Retrieves the users belonging to the configured company, which is the set assignable to numbers, ring groups and call outcomes. Used to route follow-up work to the right teammate.
- List Invites Retrieves outstanding user invitations with who was invited, by whom and when. Used to chase seats that were never accepted.
Messaging
1- Send Message Sends a real, billable SMS or MMS from a messaging-enabled company number. Media URLs turn it into an MMS. The message cannot be recalled, so it runs behind an explicit approval and never inside a retry loop, and the recipient's unsubscribe flag is respected first.
Webhooks
4- List Webhook Subscriptions Retrieves the webhook subscriptions on the company with callback URL, HTTP method and subscribed events. Used to audit which external systems are being notified of call and message activity.
- Create Webhook Subscription Registers a webhook subscription for call and message events. 800.com publishes the delivered payload only for the SMS Received event, so a real delivery is inspected before a flow depends on specific field names.
- Delete Webhook Subscription Removes a subscription so deliveries stop immediately. The subscription cannot be restored, only recreated.
- Get Webhook Delivery History Retrieves the delivery history for one subscription with the event, the response status returned and when it happened. Used to prove an event was delivered, or to detect an endpoint that has started rejecting calls.
Frequently Asked Questions
What can FlowRunner do with 800.com?
FlowRunner agents can run List Contacts, Create Contact, and Get Contact in 800.com, plus 18 more actions.
Does connecting 800.com to FlowRunner require OAuth?
No. 800.com connects to FlowRunner with an API key, no OAuth flow required.
Can 800.com trigger a FlowRunner workflow automatically?
800.com doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with 800.com
$100 in credits. No card required. Connect in minutes.