OneClick for Pipedrive
CRMComplete the round trip for OneClick for Pipedrive by Zimple, the add-on that puts custom buttons on Pipedrive deals. Agents receive the button press and run the work the salesperson just asked for.
What This Integration Enables
This connector is one half of a round trip, and understanding which half is the whole point. OneClick for Pipedrive by Zimple puts custom buttons on Pipedrive Deal, Person and Organization views. A click posts a payload to a URL you configure, which can be a FlowRunner webhook, carrying an event id plus the resource, the user id and the company id. That is the outbound half, and it is configured by hand in OneClick rather than through an API, which is why there are no triggers here. This extension supplies the inbound half: how the flow talks back to the person who clicked. No credentials are stored on the FlowRunner side, because the reply is addressed by the event id the click delivered rather than by an account.
What that buys is a shape most automation never achieves. Instead of an agent running somewhere on a schedule and reporting into a channel nobody is watching, a salesperson summons it from the record they are already reading, and gets an answer in the same view. Send Message to Pipedrive shows text in Pipedrive, up to 2000 characters including markup, permitting only the a, b, i, br and div tags with inline CSS stripped, retained for 30 days. Redirect Pipedrive User opens a URL in a new tab instead, which is how a rep lands directly on the invoice, quote or document the flow just produced. The constraints are firm and they shape the design: a reply must reach OneClick within 45 seconds of the click or it is rejected, and up to ten messages may be sent for the same click. That combination is not a limitation to work around. It is a specification for how the conversation should go, and it is close to a Flow conversation with a very short opening turn.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Generate a quote from the deal, and land on it
A rep clicks Generate Quote on a deal. Within a second the agent sends a message confirming it has the request and naming the deal, so nobody clicks twice. It pulls the line items and terms from the Pipedrive record, builds the document, writes it back to the deal as a file, and calls Redirect Pipedrive User with the document URL. The rep's browser opens on the finished quote. From their point of view they pressed a button in their CRM and a quote appeared, which is exactly the experience that gets an automation used rather than forgotten.
Enrichment and validation reported inline
A rep clicks Check This Company on an organization record. The agent runs the enrichment and validation lookups the business cares about, then reports the result as a short formatted message in Pipedrive: registration status, matched trading address, whether the VAT identifier resolves, and what disagrees with the record on screen. Where everything matches, the message says so and the rep moves on. Where something does not, the message says which field and what the source returned, so the correction takes seconds rather than a research task.
Progress on a job that takes longer than a glance
Some requests are not instant. A rep clicks Run Credit Check and the agent sends a first message acknowledging the request, then further messages as each stage returns, using the allowance of up to ten messages per click. Every one of those has to land inside the 45-second reply window, so the flow is built to report what it knows quickly rather than to hold the window open. When the work will outlast the window, the last message inside it says where the answer will appear instead of leaving the rep watching a view that has stopped updating.
Human-in-Loop Highlight
The 45-second reply window is what makes the human-in-the-loop design on this connector interesting, because no human decision fits inside it. A sales manager is not going to approve a discount in forty-five seconds, and any flow built on the assumption they might will fail on the one deal where it matters. That leaves a genuine temptation, and it is the failure this page exists to name. If the agent sends "Quote 4471 generated and sent to the customer" because that is the message it always sends, while the discount is actually sitting unapproved in a manager's queue, then the rep believes the customer has a price. They tell them so on the call. Nothing was technically broken and the damage is complete.
So the rule on this connector is that the reply window buys an acknowledgement, never a claim of completion. When a request clears the rules, the agent does the work and reports it done, with Redirect Pipedrive User taking the rep straight to the output. When it does not clear the rules, the agent spends its window telling the truth: "Discount of 22 percent on Meridian Logistics is above your 15 percent limit. Sent to Anna Beitz for approval. You will get the outcome as a note on this deal, and the quote link with it." It then routes the actual decision to the manager on a channel that has no 45-second budget, and when the answer arrives it writes the outcome onto the deal record through the Pipedrive connector, where the rep will find it. The button stays honest, the manager keeps the call that carries the money, and nobody learns the real state of a deal from a customer.
Agent Capabilities
2 actionsMessaging
2- Send Message to Pipedrive Displays a message to the Pipedrive user who clicked a OneClick button, closing the loop on what the flow did. The event id from the button's payload identifies which click to reply to, and replies must arrive within 45 seconds of the click or they are rejected. Up to ten messages can be sent for the same click, so a flow can report progress and then a final result. Messages may be up to 2000 characters including markup, permit only the a, b, i, br and div HTML tags with inline CSS stripped, and are retained for 30 days.
- Redirect Pipedrive User Opens a URL in a new browser tab for the Pipedrive user who clicked a OneClick button, without showing a message. Used to send someone straight to the document, invoice or external record the flow just produced. The event id from the button payload identifies the click, and the redirect must be issued within 45 seconds of it or it is rejected.
Frequently Asked Questions
What can FlowRunner do with OneClick for Pipedrive?
FlowRunner agents can run Send Message to Pipedrive and Redirect Pipedrive User in OneClick for Pipedrive.
Does connecting OneClick for Pipedrive to FlowRunner require OAuth?
No. OneClick for Pipedrive needs no credentials at all, so there is no key to obtain, store, or rotate.
Can OneClick for Pipedrive trigger a FlowRunner workflow automatically?
OneClick for Pipedrive doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with OneClick for Pipedrive
$100 in credits. No card required. Connect in minutes.