OnePageCRM
CRMConnect AI agents to OnePageCRM, an action-focused sales CRM that turns every contact into a next action. Agents create contacts and deals, set the next action, log calls and meetings, and post notes against a record.
What This Integration Enables
OnePageCRM is built around one refusal: it will not let a contact sit in the database without a defined next step. Every contact carries exactly one next action, and the interface is organised around clearing that list rather than browsing a pipeline. That is a genuinely opinionated product decision and it is the thing to design around, because it means the most consequential write this integration performs is not creating a record, it is deciding what a salesperson does next. Create Action sets the next action, its status controls the scheduling behaviour through As Soon As Possible, On Date, At Date and Time, Waiting, and Queued, and Mark Action As Done completes it and advances the contact. An agent working here is not filling a CRM, it is loading a queue that a person will work through tomorrow morning.
The rest of the surface supports that model without complicating it. Contacts have full lifecycle coverage, and Change Contact Status moves a person between Lead, Prospect, and Customer while Assign Tag To Contact and Unassign Tag From Contact carry segmentation. Deals attach to a contact rather than standing alone, so Create Deal requires a contact id, a name, an owner, and an amount, with status limited to Pending, Won, or Lost and the pipeline stage expressed as a numeric position within a pipeline. Log Call and Log Meeting take the event time as a Unix timestamp in seconds through callTime and meetingTime, and Create Action can carry a time of day as seconds since midnight in exactTime, so a telephony or calendar flow writes the moment the thing actually happened rather than the moment the flow got round to it. Companies are read and updated here but not created through this connector, so a company record arrives with its contact rather than ahead of it. Two operational facts are worth internalising. Deletes are irreversible, and Delete Contact takes the contact's actions, notes, calls, and deals with it. And this connector ships no triggers: OnePageCRM offers no webhook subscription through it, so change detection is a scheduled poll on List Contacts, List Deals, or List Actions with page and perPage, where the page size is capped at 100 and page_data carries the total count. Authentication is HTTP Basic, with the OnePageCRM user_id as the username and the api_key as the password, both taken from the API tab of the account.
Without FlowRunner
With FlowRunner
Use Case Scenarios
An inbound lead that arrives with its follow-up already scheduled
A demo request or a booked meeting from Calendly starts the run. The agent calls List Contacts filtered on the email address to see whether this person is already known, and where nothing matches it calls Create Contact with the name, company, email, phone, lead source, and the tags that describe where the lead came from. Create Deal then opens the opportunity against that contact with the owner resolved from the routing rules and an estimated amount, so the deal exists in the pipeline rather than in someone's intention to add it. Create Action sets the next action to a preparation task with a status of On Date so it surfaces the morning before the meeting rather than immediately. Create Note records what the form actually said, which is the context the rep will want and the form itself will not keep.
A call log that reaches the record with its real timestamp
A telephony platform reports a completed call. The agent resolves the contact through List Contacts, then calls Log Call with the outcome and callTime set to the Unix timestamp of the call itself rather than of the flow run, because a history that records when the automation caught up is not a history. Where the call produced a commitment, Mark Action As Done clears the next action that prompted the call and Create Action sets the one that follows from it. Where the conversation moved the relationship on, Change Contact Status promotes the contact from Lead to Prospect and Assign Tag To Contact applies the segment that decides which sequences the person belongs in. The substance goes into Create Note so the reasoning survives past the rep who heard it.
A pipeline review that reads without writing
On a schedule the agent calls List Deals filtered by status, owner, or pipeline, paging with page and perPage inside the cap of 100 and reading page_data for the total so a truncated page is never mistaken for a short list. For each open deal it calls Get Contact and List Actions to check whether a next action actually exists and when it is due, which is the only signal in this product that tells you a deal is being worked rather than merely open. The joined view lands in Google Sheets and a per-owner summary posts to Slack, naming deals above a value threshold whose contact carries no scheduled next action at all. Nothing is written back, which is what makes it safe to run every morning.
Human-in-Loop Highlight
In most CRMs the write to gate is a delete, and Delete Contact here is genuinely severe because it removes the contact along with its actions, notes, calls, and deals. But the operation that will actually cause an argument is Create Action, and it will do so without erroring, without deleting anything, and without anyone noticing until the standup. OnePageCRM gives each contact exactly one next action. That is the product. So when an agent runs Create Action across a segment, it does not add a task to a list, it replaces whatever that contact was already pointed at. The rep who spent Friday afternoon deciding that the Ashford account needed a pricing conversation on Tuesday opens the app on Monday and finds a generic nurture step in its place, with no record that anything was displaced, because the previous action is simply gone. Multiply that by a two hundred contact segment and you have quietly rewritten a team's week. So the agent reads before it writes. It calls List Actions across the target segment, separates the contacts whose next action is unset or was set by a previous run of this same flow from the ones a person set by hand, and posts to the sales manager: "Nurture sequence ready for 214 contacts. 158 have no next action or carry one this flow set previously, and I will set those without asking again. 56 carry a next action set by a person: 31 are dated this week, 9 are marked At Date and Time, and 4 sit on deals above 25k that are already Pending. Setting mine replaces theirs and the originals are not recoverable. Skip the 56, overwrite them, or overwrite only the ones with no date?" The manager answers once, the agent applies that rule, and Create Action runs only where a person agreed it should. This is the human-in-the-loop moment on a CRM whose single next action field is its best feature and its sharpest edge, because an agent can see that a slot is occupied and only a person can say whose plan wins.
Agent Capabilities
23 actionsContacts
8- List Contacts Returns contacts with `page` and `perPage`, capped at 100 per page, with `page_data` carrying the total count. This is the scheduled read that substitutes for the events this connector does not receive.
- Get Contact Retrieves a single contact with its current status, tags, and owner. Used to confirm state before a change is composed.
- Create Contact Creates a contact with company, email, phone, tags, and lead source. At least a first or last name is required, and the Email and Phone parameters each take a single value with a type.
- Update Contact Updates an existing contact. Used to enrich a record from another system without disturbing the fields the sales team owns.
- Delete Contact Permanently removes the contact along with its related actions, notes, calls, and deals. There is no recovery through this connector.
- Change Contact Status Moves a contact between statuses such as Lead, Prospect, and Customer. Used to reflect a promotion decided in a conversation or another system.
- Assign Tag To Contact Applies a tag for segmentation, which is how a contact ends up in the right campaign or report.
- Unassign Tag From Contact Removes a tag from a contact, used when a segment no longer describes the relationship.
Companies
3- List Companies Returns company records with paging. Used to see the accounts behind a set of contacts.
- Get Company Retrieves a single company record.
- Update Company Updates a company record. This connector reads and updates companies but does not create them, so a company arrives with its contact rather than ahead of it.
Deals
5- List Deals Returns deals filtered by status, owner, or pipeline, with paging. Used for pipeline reporting and for finding deals that have gone quiet.
- Get Deal Retrieves a single deal with its amount, owner, and stage.
- Create Deal Creates a deal against a contact. Requires a contact id, a name, an owner, and an amount, with status one of Pending, Won, or Lost and the stage expressed as a numeric position within a pipeline.
- Update Deal Updates a deal, including moving it between stages and marking it Won or Lost.
- Delete Deal Permanently removes a deal and cannot be undone through this connector.
Next actions
3- List Actions Returns the next actions currently set across contacts. This is the read that tells a flow which contacts already carry a plan, and the one that has to run before any bulk Create Action.
- Create Action Sets a contact's next action, with a status of As Soon As Possible, On Date, At Date and Time, Waiting, or Queued controlling when it surfaces, and `exactTime` carrying a time of day as seconds since midnight. Because each contact has exactly one next action, this replaces whatever was there.
- Mark Action As Done Completes the current next action and advances the contact, which is how a flow closes the loop it opened rather than leaving stale steps behind.
Activity
4- List Notes Returns the notes recorded against contacts, used to read what is already known before adding to it.
- Create Note Writes a note against a contact, preserving the substance of a conversation where the next person will find it.
- Log Call Records a completed call with its outcome and `callTime` as a Unix timestamp in seconds, so the history reflects when the call happened rather than when the flow ran.
- Log Meeting Records a meeting with `meetingTime` as a Unix timestamp in seconds. Used by calendar and conferencing flows to close the gap between what happened and what the CRM knows.
Frequently Asked Questions
What can FlowRunner do with OnePageCRM?
FlowRunner agents can run List Contacts, Get Contact, and Create Contact in OnePageCRM, plus 20 more actions.
Does connecting OnePageCRM to FlowRunner require OAuth?
No. OnePageCRM connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can OnePageCRM trigger a FlowRunner workflow automatically?
OnePageCRM doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with OnePageCRM
$100 in credits. No card required. Connect in minutes.