BurstyAI

Run BurstyAI no-code SEO, content, and outreach workflows from a flow through the Workflow API. Agents kick off a content or backlink task and collect the finished result without leaving FlowRunner.

6 actions API key available

BurstyAI website ↗ Platform Documentation ↗ Capability data verified 2026-08-01

Weekly content sprint opens and the keyword sheet is marked ready

Agent reads the queued rows and the column headers from the source sheet

Agent confirms every workflow parameter key maps to a real sheet column

Agent counts the rows the batch would touch and resolves the cron expression and time zone

Agent calls Run Workflow on the first row alone and polls Get Job Result for a sample

Content lead receives the sample output, the row count and the proposed schedule

Content lead authorizes Schedule Workflow In Bulk, which no action in this connector can cancel

What This Integration Enables

BurstyAI is a workflow tool, which makes this an unusual integration: a runner inside a runner. The connector treats a BurstyAI workflow as a single callable capability. An agent starts one with Run Workflow, gets a job ID back immediately, polls Get Job Result until the job reports finished, and reads the accumulated output. When the job produced files, Get File Download URLs turns BurstyAI storage object IDs into URLs the flow can actually fetch. Nothing runs synchronously, and the connector is built around that: the finished flag on Get Job Result lets a flow branch on completion without parsing a status string.

The scale actions are where this earns its place. Run Workflow In Bulk executes a workflow once per row of a BurstyAI sheet, with each parameter supplied as a column name rather than a literal, so one call can drive a whole content backlog. Schedule Workflow and Schedule Workflow In Bulk hand the cadence to BurstyAI itself on a cron expression. That last capability is worth reading carefully, because a schedule registered inside BurstyAI keeps running on BurstyAI's clock, and this connector exposes no action to stop it. Starting something you cannot stop from the same place is exactly the moment human-in-the-loop stops being a nice-to-have.

Without FlowRunner

Two schedulers, one calendar Recurring BurstyAI runs live in a second dashboard that nobody opens between sprints

Batches launched blind A bulk run starts against a sheet whose row count and column mapping were never checked

Output stranded in the tool Finished articles, research and generated files wait in BurstyAI until someone exports them

With FlowRunner

One place the work is visible Every run is a flow step carrying its own job ID, status and accumulated output

Batch size approved before launch A sample run and a row count reach a named owner before the full batch starts

Results land where work happens Job output and file download URLs move straight into the CMS, the sheet or the channel

Use Case Scenarios

A Keyword Backlog Turned Into Drafts, One Sample First

The content sprint opens and a sheet of approved keywords is marked ready. The agent pulls the rows from Google Sheets, reads the column headers, and checks them against the parameter keys the selected BurstyAI workflow requires, which carry a workflow-specific prefix and are easy to get wrong. Instead of launching the batch, it runs the workflow once against the first row with Run Workflow, polls Get Job Result, and posts the single finished draft to the content channel next to the row count the full batch would process. The lead reads one real output rather than approving an abstraction, then the agent calls Run Workflow In Bulk for the rest.

Company Research Attached to an Inbound Lead

A new lead lands in HubSpot with nothing but a company website. The agent calls Run Workflow with the research workflow and the URL as its parameter, polls Get Job Result every few seconds until the status reaches END, and writes the returned company summary back onto the CRM record before the rep opens it. If the job comes back ERROR, the agent logs the failure as one of the automation exceptions the flow tracks rather than leaving a silently empty field on the record.

Collecting the Output of a Schedule BurstyAI Owns

A recurring workflow was registered with Schedule Workflow and now produces output on BurstyAI's clock. A FlowRunner flow runs on its own timer, calls Get Job Result for the registered job ID, and picks up any new accumulated output. Where the workflow produced images or documents, the agent passes the storage object IDs to Get File Download URLs and pushes the fetched files into the CMS. The schedule lives in BurstyAI; the record of what it produced, and who reviewed it, lives in the flow.

Human-in-Loop Highlight

The gate sits in front of Schedule Workflow In Bulk, because that single call combines the two properties this connector cannot walk back: it runs once per row of a sheet the flow never sees the contents of, and it repeats on a cron schedule registered inside BurstyAI, where none of the six available actions can cancel it. Before the agent makes that call, it posts to the content lead: "Ready to schedule [workflow] across [N] rows of sheet [name], running [cron expression] in [time zone]. Sample output from row 1 attached. Once this is registered, BurstyAI owns the schedule and this flow can only read results, not stop it. Confirm, change the cadence, or run it once manually?" The lead is approving a standing commitment of credits and output volume, not a single job, and the message says so.

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

6 actions

Running Workflows

Run Workflow Starts one execution of a BurstyAI workflow and returns a job ID straight away. Used when a flow needs a single content, research or outreach task done and will poll for the result: drafting one article, researching one company, expanding one brief.
Run Workflow In Bulk Runs a workflow once per row of a BurstyAI sheet, with each parameter supplied as a column name rather than a literal value so BurstyAI substitutes the row data. Used to process a whole backlog in one call, and the action to put behind an approval because the row count decides the spend.

Scheduling

Schedule Workflow Registers a workflow to run repeatedly on a cron schedule inside BurstyAI. Used when the cadence belongs to the content tool rather than the flow, for example a weekly article slot that should keep running whether or not a flow fires.
Schedule Workflow In Bulk Registers a sheet-driven bulk run on a recurring cron schedule, combining batch execution with BurstyAI-side scheduling. Used for standing content programs, and the highest-consequence action in the connector because the flow has no way to unregister it afterwards.

Results and Files

Get Job Result Returns the current status and accumulated output of a job. Used as the polling step after every run and schedule action, and as the branch point once the job reports finished, whether it ended in success or error.
Get File Download URLs Converts BurstyAI storage object IDs into downloadable URLs. Used when a workflow produced images or documents that need to reach a CMS, a storage bucket or an approval message rather than staying inside BurstyAI.

Frequently Asked Questions

What can FlowRunner do with BurstyAI?

FlowRunner agents can run Run Workflow, Schedule Workflow, and Run Workflow In Bulk in BurstyAI, plus 3 more actions.

Does connecting BurstyAI to FlowRunner require OAuth?

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

Can BurstyAI trigger a FlowRunner workflow automatically?

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

Start building with BurstyAI

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

Start Building Free Talk to us