Digiclose
CRMConnect AI agents to Digiclose, a phone sales and sales automation platform. Agents create contacts, move them through pipelines, log transactions, assign tasks, and manage team and product records.
What This Integration Enables
Digiclose is built for teams that still sell on the phone, and it is unapologetic about it. The object model is a pipeline, a deal phase, a team, a member, and a contact who is really a lead, plus transactions that record the money when the call goes well. That combination tells you what the platform is for: getting the right lead in front of the right closer fast enough that the phone is still warm. An agent working here is not tidying a database. It is feeding a calling floor, and the value of the automation is measured in whether the person whose job is to dial has something worth dialling.
Two things shape how flows are built against it. Contact fields are defined per account, so create and update take a Fields object keyed by each field's internal name, and Get Contact Fields is the action that tells you what those names, types, and dropdown options actually are on this account. Any import that skips that read is guessing. And on update, setting a field value to the sentinel OC_DELETE_COLUMN clears it, which is a real capability and a real hazard in the same breath. Digiclose ships no triggers to FlowRunner. The vendor documents a webhook subscription API and per event payloads, and this connector manages subscriptions through Subscribe To Webhook and Unsubscribe From Webhook, but the per webhook signing secret is returned only at creation time and cannot be threaded through the connector's event handling, so a realtime trigger was deferred rather than shipped unverified. Change detection is a polling pattern instead: List Recent Webhook Events returns up to one hundred recent events filterable by type, covering contact_created, contact_deal_phase_changed, task_completed, offer_seen, offer_accepted, and the rest of the documented set. Paging is small and explicit, twenty five per page on List Contacts and fifty on List Products and List Transactions, which keeps a poll honest about how much it is really pulling. Digiclose is developed and hosted in Germany.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Ad leads that arrive already routed to a closer
Paid leads land as rows in Google Sheets from several campaigns. Before the first write, the agent calls Get Contact Fields once to load the account's internal field names and the options on each dropdown, then calls List Pipelines and Get Pipeline Deal Phases to resolve the entry phase, and List Teams For Deal Phase to find which team owns it. Each row becomes a Create Contact with a Fields object built from the real internal names, assigned to the pipeline, deal phase, team, and member that owns that campaign's traffic. Create Task then schedules the first call against the contact with the right task category, pulled from List Task Categories. Rows whose campaign does not map to a known team are held out and reported rather than dumped into a default queue where nobody owns them.
An accepted offer that closes the loop before anyone opens the CRM
On a schedule, the agent polls List Recent Webhook Events filtered to offer_accepted. For each event it calls Get Contact to load the customer, then Create Transaction against the product and the contact, supplying either the Contact ID or the Contact Email that Digiclose requires to identify the customer, with the currency set to Euro (EUR) or US Dollar (USD) as the deal was quoted. The sale is appended to a revenue sheet, and the customer receives a confirmation and next steps through Brevo. Create Task then schedules the onboarding call against the same contact, so the handover from closing to delivery exists as a record rather than as a promise made on a call.
A calling floor that knows which leads have gone cold
The agent polls List Contacts through its pages, and for each contact calls Get Contact Tasks and Get Contact Notices to see what has actually happened on the record. Leads sitting in an early deal phase with no completed task and no notice past a threshold the team sets are gathered into a list, grouped by member using List Teams and Get Team Members. Each closer receives their own list in Slack naming the leads, how long they have been idle, and the source that produced them. Nothing is reassigned automatically, because a lead going quiet is a conversation between a manager and a rep, not a database operation.
Human-in-Loop Highlight
The dangerous write in Digiclose is not the delete. It is Update Contact carrying OC_DELETE_COLUMN. That sentinel is how the API clears a field, and it exists for a good reason: without it there is no way to remove a value that should no longer be there. But it turns an ordinary sync into a destructive one under a very ordinary condition. A source spreadsheet exports an empty cell. A form field goes unanswered. A CRM export loses a column. If the flow maps empty to the clear sentinel, then a routine enrichment run walks the pipeline and erases the mobile numbers, the objection notes, and the qualification answers that closers wrote down during real calls, on records that otherwise look completely untouched. Because contact fields are account defined, nobody notices until a rep opens a lead before dialling and the history is not there. So the agent never sends the sentinel on its own authority. It builds the update set, separates the writes that set a value from the writes that would clear one, and posts to the sales manager in Slack: "Nightly enrichment covers 214 contacts. 197 are pure updates. 17 would clear a field because the source cell is empty: 11 clear a secondary phone, 4 clear the qualification note, and 2 clear the objection field on leads with a completed call in the last week. Apply the 197 now, and clear the 17, or skip them?" The manager decides. In almost every case the answer is to apply the updates and skip the clears, because an empty cell in an export is much more often a missing column than a fact about the customer. This is the human-in-the-loop moment that keeps a helpful nightly job from quietly deleting the only record of what a customer said.
Agent Capabilities
34 actionsContacts
7- List Contacts Returns contacts (leads) with Page and Results Per Page paging, up to twenty five per page. Used for sweeps, idle lead detection, and reporting.
- Get Contact Retrieves a single contact with its account defined field values. Used to load full context before a task, a transaction, or an update.
- Create Contact Creates a lead from a `Fields` object keyed by internal field name, assigned to a pipeline, deal phase, team, and member. Used to route inbound leads to the closer who owns that source.
- Update Contact Updates a contact from a `Fields` object. Setting a value to `OC_DELETE_COLUMN` clears that field, which is the write held behind human approval.
- Get Contact Notices Returns the notices recorded against a contact. Used to judge whether a lead has actually been worked before escalating it.
- Get Contact Tasks Returns the tasks attached to a contact. Used to detect leads with no scheduled follow up and to confirm a call actually happened.
- Get Contact Fields Returns the account's contact field internal names, types, and dropdown options. This is the read that makes every other contact write correct, and it runs before any import commits.
Pipelines
3- List Pipelines Returns the pipelines configured on the account. Used to resolve where a lead should enter before it is created.
- Get Pipeline Retrieves a single pipeline. Used to confirm the pipeline a flow is about to write into is the one intended.
- Get Pipeline Deal Phases Returns the deal phases within a pipeline. Used to resolve the entry phase for new leads and to interpret phase change events.
Products
4- List Products Returns the product catalog with Page and Results Per Page paging, up to fifty per page. Used to resolve a product before recording a sale.
- List Recent Products Returns recently created or changed products. Used as a lightweight poll to keep an external catalog in step.
- Get Product Retrieves a single product with its currency and price. Used to validate a transaction before it is written.
- Create Product Creates a product, with amounts in Euro (EUR) or US Dollar (USD). Currency defaults to the company currency. Used to keep the sellable catalog aligned with an external source.
Tasks
6- List Tasks Returns tasks across the account. Used for follow up coverage reporting.
- List Recent Tasks Returns recently created or changed tasks. Used as the polling target for detecting new follow up work.
- Get Task Retrieves a single task with its category and target contact. Used to confirm state before acting on it elsewhere.
- Create Task Creates a task against a contact. Used to schedule the follow up call in the same run that captured the lead.
- List Task Categories Returns the task categories available on the account. Used to resolve a real category id rather than writing a task with none.
- Create Task Category Creates a task category. Used when a new motion needs its own follow up type on the calling floor.
Teams
5- List Teams Returns the teams on the account. Used to resolve ownership before routing a lead.
- Get Team Retrieves a single team. Used to confirm a routing destination.
- Get Team Members Returns the members of a team. Used to assign a specific closer and to group reporting by rep.
- List Teams For Deal Phase Returns the teams that own a given deal phase. Used to route a lead to the team responsible for the phase it is entering.
- Create Team Creates a team. Used when a new campaign or region needs its own calling group.
Transactions
4- List Transactions Returns transactions with Page and Results Per Page paging, up to fifty per page. Used for revenue reporting and reconciliation.
- List Recent Transactions Returns recently recorded transactions. Used as the polling target for pushing sales into accounting or reporting tools.
- Get Transaction Retrieves a single transaction. Used to confirm an amount and currency before it is mirrored elsewhere.
- Create Transaction Records a sale against a product and a customer, identified by either a Contact ID or a Contact Email. Quantity defaults to 1 and currency defaults to EUR. Used to close the loop between an accepted offer and the finance system.
Users
2- List Users Returns the users on the account. Used to resolve an owner or assignee.
- Get User Retrieves a single user. Used to attach a real name to a routing decision or a report.
Webhooks
3- List Recent Webhook Events Returns up to one hundred recent webhook events, filterable by event type across the documented set including `contact_created`, `contact_deal_phase_changed`, `task_completed`, `offer_seen`, and `offer_accepted`. This is the polling surface that stands in for a realtime trigger.
- Subscribe To Webhook Registers a webhook subscription so an external endpoint of your choosing receives Digiclose events. The per subscription signing secret is returned only in this response, so verification state has to be kept on the receiver.
- Unsubscribe From Webhook Removes a webhook subscription. Used to retire a receiver, and worth confirming, because delivery stops without any further signal.
Frequently Asked Questions
What can FlowRunner do with Digiclose?
FlowRunner agents can run List Contacts, Get Contact, and Create Contact in Digiclose, plus 31 more actions.
Does connecting Digiclose to FlowRunner require OAuth?
No. Digiclose connects to FlowRunner with an API key, no OAuth flow required.
Can Digiclose trigger a FlowRunner workflow automatically?
Digiclose doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Digiclose
$100 in credits. No card required. Connect in minutes.