Discko
Sales IntelligenceConnect AI agents to Discko, an AI lead qualification widget embedded in your site. Agents read qualified leads together with the qualification context the widget captured, and update each lead's status as it moves to won or lost.
What This Integration Enables
Discko inverts what a website chat widget normally does. It does not answer visitor questions, it asks them, running an adaptive conversation that collects contact and company details and scores each lead on fit, intent, and overall quality. That distinction matters more than it sounds, because it changes the provenance of the data. Everything Discko hands your agent was typed by the person it describes, in a conversation they chose to have. Compared with an enrichment vendor that resolves a stranger from a public profile, this is first-party material and it comes with the reasoning attached.
The connector is deliberately small and we would rather say so than pad the list. There are three actions. Get All Leads returns the entire lead list in a single response with no pagination parameters, so a flow can hold the whole set at once. Get Lead returns one record by its identifier. Update Lead Status is the only write, moving a lead between New, In Progress, Won, and Lost. That surface is a thesis rather than a gap: Discko is a capture and scoring instrument, and the pipeline it feeds lives in your CRM, not in Discko. The right shape for a flow here is read the truth out, decide elsewhere, then write the one field back that closes the loop.
There are no triggers on this connector, and it is worth being exact about why. Discko delivers new-lead events by outbound webhook configured in its dashboard under Settings, Integrations, Webhooks, not through an API subscription an extension could manage. So FlowRunner does not receive Discko events natively. A scheduled Get All Leads is the supported pattern, and if you need real-time delivery you point the dashboard webhook at a FlowRunner inbound endpoint yourself. The vendor documents retries with exponential backoff and does not currently sign those deliveries, which is a detail worth knowing before you treat the payload as trusted.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The scored lead reaches the CRM with its evidence intact
A scheduled flow calls Get All Leads and diffs the result against what already exists in HubSpot. For each lead that is new, the agent creates the contact and writes the fit, intent, and overall scores into custom properties, then attaches the needs summary as a note on the record. That last step is the one teams skip and later regret. A rep who opens a contact showing an intent score of 9 has no idea what to say; a rep who opens the same contact and reads two sentences the buyer typed about a renewal deadline knows exactly how to open. The agent finishes by calling Update Lead Status to move the lead to In Progress, so the Discko dashboard and the CRM stop disagreeing about who has been picked up.
High-intent leads interrupt the day, the rest do not
Not every lead deserves a notification, and a channel that pings for all of them gets muted within a week. A flow reads the lead list, applies a threshold the team set on the overall score, and for the leads above it posts to Slack with the company details, the needs summary, and a direct link. Everything below the threshold is appended to a Google Sheets tab for the weekly review instead. The agent is not deciding who is worth talking to, it is deciding what deserves to break someone's concentration right now. That is a much safer thing to automate, and it is reversible in a way that a disqualification is not.
Closing the loop after a human actually talks to someone
A rep replies to a lead through Gmail and the thread is picked up by a flow. The agent calls Get Lead to confirm the record's current status, and if the lead is still sitting at New it calls Update Lead Status to move it to In Progress. When the deal later closes in the CRM, a second flow writes Won back to Discko. The point of the round trip is that Discko's own reporting on which qualification scores actually converted is only as honest as the outcomes written back into it. Left alone, the scoring model gets graded on a dataset where every lead is permanently New.
Human-in-Loop Highlight
Update Lead Status is the only write this connector has, and its Lost value is the one that deserves a person. Setting a lead to Lost is not technically irreversible, the API will happily set it back, but the practical effect is that the lead leaves every follow-up queue built on top of that status and nobody looks at it again. What makes it worth stopping on is what the decision rests on. Discko's fit, intent, and overall scores are a model's reading of an adaptive conversation, and the vendor's own documentation notes that the exact field shape inside the lead object should be confirmed against a real response rather than assumed. A flow that reads overall below a number and writes Lost is letting one model's opinion of a stranger's typing close a door on a real company, and Discko records no reason for the change. So the agent does the assembly and hands over the judgment. It calls Get Lead for the full record, pulls the needs summary and the company details, and asks the pipeline owner in Slack: "Discko lead 4412, Nordwind Logistik, overall 3, intent 7. Their stated need reads 'evaluating for Q1, need SOC 2 before we can sign'. Score says drop, words say early not unqualified. Set Lost, or move to In Progress and route to enterprise?" A score and a sentence pointing in different directions is exactly the case no threshold handles, and human-in-the-loop here is not caution, it is what makes the other several hundred automatic syncs safe to leave alone.
Agent Capabilities
3 actionsReading Leads
2- Get All Leads Retrieves every lead captured by your Discko qualification widget. Each lead includes its id, current status, contact information, company details, the AI qualification scores for fit, intent, and overall, and a summary of the visitor's stated needs. The full list comes back in one response with no pagination parameters, which makes this the natural read for a scheduled reconciliation against a CRM.
- Get Lead Retrieves a single lead by its identifier, returning the same full object including status, contact and company details, the three qualification scores, and the needs summary. Returns a LEAD_NOT_FOUND error when nothing matches the supplied id. Use it as the confirmation read before a status write, so the flow acts on the record's current state rather than on a stale copy from an earlier list call.
Pipeline Status
1- Update Lead Status Updates the pipeline status of a single lead to New, In Progress, Won, or Lost, returning the updated lead on success. It answers with LEAD_NOT_FOUND for an unmatched id and INVALID_STATUS for a value the API does not accept. This is the connector's only write, and it is the field that decides whether Discko's own reporting on score quality is measured against real outcomes or against a pipeline frozen at New.
Frequently Asked Questions
What can FlowRunner do with Discko?
FlowRunner agents can run Get All Leads, Get Lead, and Update Lead Status in Discko.
Does connecting Discko to FlowRunner require OAuth?
No. Discko connects to FlowRunner with an API key, no OAuth flow required.
Can Discko trigger a FlowRunner workflow automatically?
Discko doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Discko
$100 in credits. No card required. Connect in minutes.