FlowRunner
PricingContact
Theme
Start Free

Run business operations in Flowlu end to end. Agents manage CRM accounts and leads, create projects and tasks, and read invoices, connecting sales activity to delivery work in one system.

9 actions API key available
Flowlu website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
A deal closes in the CRM, or an inbound inquiry lands from the intake form
List CRM Accounts confirms whether the company already exists in Flowlu before anything is written
Create CRM Account adds the company with its contact details when it is genuinely new
The delivery lead confirms scope, owner, and start date, because opening a project commits real people to real hours
Create Project opens the delivery project, named for the account and engagement
Create Task lays down the kickoff tasks with priority and deadline set
The team channel receives the project link, the owner, and the first deadline
A weekly List Invoices sweep reconciles billing against the projects now underway

What This Integration Enables

Flowlu's bet is that small teams should run sales, delivery, and billing in one system, so the thread from lead to project to invoice never leaves the building. The thread still breaks, though, at exactly the moments no software module owns: the handoff from closed deal to opened project, the gap between work delivered and work invoiced. FlowRunner agents work those seams. They create accounts when customers first appear, open projects and kickoff tasks the moment a person approves the start, and sweep leads and invoices into reports on a schedule. - Create CRM accounts in Flowlu when new customers arrive from forms, storefronts, or other CRMs - Open projects and kickoff tasks the moment an engagement is approved, with [human-in-the-loop](/concepts/human-in-the-loop) sign-off before work is committed - Sync leads, projects, tasks, and invoices into spreadsheets for pipeline, delivery, and billing visibility - Alert the team in chat when new leads or invoices appear - Look up full account records by ID to enrich downstream workflow steps

Without FlowRunner

The handoff gap A deal closes on Tuesday and delivery finds out on Friday, because the handoff lives in someone's inbox
Delivery starts from memory Kickoff tasks get recreated by hand for every engagement, and the steps that get skipped are the ones that bite later
Three modules, three exports Pipeline, project status, and billing each require someone to pull a report before anyone can see the whole thread

With FlowRunner

Won means underway The account, project, and kickoff tasks exist minutes after a person approves the start, not days after the close
Kickoff as a standing pattern Every approved engagement opens with the same task structure, priorities, and deadlines, applied by the agent
One thread, read continuously Leads, projects, and invoices flow into scheduled reports, so the lead-to-cash story is visible without an export

Use Case Scenarios

Inquiry to opened engagement without the inbox relay

An inbound inquiry arrives through [Typeform](/integrations/typeform). The agent checks List CRM Accounts for the company, calls Create CRM Account when it is new, and drafts the proposed project. The delivery lead reviews the scope summary and approves. Create Project opens the engagement and Create Task lays down the kickoff checklist with deadlines. The gap between "they want to work with us" and "we are working" shrinks from days to the length of one approval.

Won deals in HubSpot become delivery work in Flowlu

Sales runs in [HubSpot](/integrations/hubspot); delivery runs in Flowlu. On a schedule, the agent pulls newly won deals, and for each one creates the Flowlu project and the standard kickoff tasks, assigning priority and deadline from the deal's close date. Delivery stops depending on a human remembering to copy a deal across systems, and every engagement starts with the same structure.

The lead-to-cash report that assembles itself

Every Monday, the agent runs List Leads and List Invoices, pages through the results, and writes them to [Google Sheets](/integrations/google-sheets): pipeline by stage and value on one tab, invoices by status and total on another. When a new lead appears mid-week, a [Slack](/integrations/slack) alert goes to the sales channel with the lead's name, stage, and value. The operations review starts from live numbers instead of somebody's Sunday-night export.

Human-in-Loop Highlight

The costly operation in this connector is not a delete. It is Create Project. Opening a project in Flowlu is the signal that puts a delivery team to work: tasks get assigned, hours get logged, and an invoice eventually follows, all downstream of that one write. An agent that opens projects on every strong-looking signal fills the delivery calendar with commitments nobody scoped. So the agent does everything up to the commitment, resolves the account, drafts the project name, proposes the kickoff tasks, and then asks the delivery lead: this client, this scope, this start date. Only after that answer do Create Project and Create Task fire.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

9 actions

CRM Accounts

3
  • List CRM Accounts Retrieves a paginated list of CRM accounts, companies and contacts, with their name, type, contact details, and identifiers. The existence check that runs before any account is created.
  • Create CRM Account Creates a new CRM account, company or contact, with the provided name and optional contact details. Returns the new record including its assigned ID.
  • Get CRM Account Retrieves a single CRM account by ID with its full record: name, type, contact information, and status. Used to enrich downstream steps with real account context.

CRM Leads

1
  • List Leads Retrieves a paginated list of leads with their name, stage, associated account, and value. The feed behind pipeline reports and new-lead alerts.

Projects

2
  • List Projects Retrieves a paginated list of projects with each project's name, status, and identifiers. Used to check what is already underway before opening anything new.
  • Create Project Creates a new project with the provided name and optional description. The commitment step this page's human gate exists for.

Tasks

2
  • List Tasks Retrieves a paginated list of tasks with each task's name, description, status, and due date. Used to read delivery state into reports and follow-up workflows.
  • Create Task Creates a new task with name and optional description, priority, and deadline. The step that turns an approved engagement into assigned work.

Invoices

1
  • List Invoices Retrieves a paginated list of sales invoices with each invoice's number, total, status, and associated account. The billing side of the lead-to-cash report.

Frequently Asked Questions

What can FlowRunner do with Flowlu?

FlowRunner agents can run List CRM Accounts, Create CRM Account, and Get CRM Account in Flowlu, plus 6 more actions.

Does connecting Flowlu to FlowRunner require OAuth?

No. Flowlu connects to FlowRunner with an API key, no OAuth flow required.

Can Flowlu trigger a FlowRunner workflow automatically?

Flowlu doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Flowlu

$100 in credits. No card required. Connect in minutes.