Hexomatic
Developer ToolsControl Hexomatic no-code web scraping and data extraction workflows from FlowRunner. Agents launch a scrape, wait for it to finish, and pull the tabular results into the next step.
What This Integration Enables
Hexomatic is the only service in this part of the catalog where FlowRunner does not describe the scrape. Someone on your team already built the recipe in Hexomatic's no-code builder, chaining its automations together and pointing them at the sites they care about. This connector is the control plane over that work, not a replacement for it. It lists the workflows on the account with their steps and current status, pulls the tabular result set a completed run produced, reads the execution log when a run went wrong, switches schedules on and off in bulk, and deletes workflows outright.
That is a deliberately small surface, and the smallness is the point. The scraping recipe lives where a person can see it and change it. FlowRunner supplies the two things a builder inside Hexomatic cannot: the moment the results arrive, and everything that should happen next. On Workflow Status Change is what closes that loop, emitting an event when a workflow's execution status changes rather than leaving a flow to poll for a file that may not exist yet.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Scraped prospects into the CRM the moment a run finishes
A revenue operations team runs a nightly Hexomatic workflow that collects company listings from an industry directory. When On Workflow Status Change reports the run completed, the agent calls Get Workflow Data, reads the headers and rows, discards records with no usable domain, checks each remaining company against HubSpot, and creates only the ones that are genuinely new. The counts go to Slack so the team can see what last night's run was actually worth rather than assuming.
Diagnosing a run that produced nothing
A monitoring workflow that normally returns two hundred rows returns zero. Rather than rerunning it and hoping, the agent calls Get Workflow Logs and reads the entries, each carrying the timestamp of an event and a description of the operation performed, such as an automation starting or input data passing between steps. The agent posts the point at which the run stopped progressing alongside the last successful run's row count, so whoever owns the recipe knows whether an automation failed or the source site stopped returning results.
Turning scraping spend off when the campaign ends
A set of workflows was activated for a specific campaign. When the campaign end date passes in the project tracker, the agent calls Update Workflow Status to deactivate exactly those workflows in one call. The workflows and every row they collected stay intact; only the automatic runs stop. If the campaign gets extended, the same action reactivates them without anyone rebuilding a recipe.
Human-in-Loop Highlight
Delete Workflows is the operation that earns a gate on this connector, and it earns one for a specific reason: it removes the workflows together with the data they collected, it accepts a list rather than a single item, and it cannot be undone. A tidy quarterly maintenance flow that sweeps up workflows nobody has run in ninety days is exactly the kind of automation that looks harmless right up to the moment it takes the historical result set somebody was still citing. So the agent assembles the candidate list and stops there. It posts to the operations channel: "Nine Hexomatic workflows have had no status change in 90 days. Here they are with their names, last status and the row count Get Workflow Data currently returns for each. Deactivate all nine, or delete these specific ones permanently?" Deactivating through Update Workflow Status is the reversible move and the agent's default recommendation. Deleting is the one it hands to a person, because a permanent deletion of collected data is not an automation exception to be resolved by rule, it is a decision with an owner.
Agent Capabilities
5 actionsWorkflows
5- List Workflows Retrieves the automation workflows on the account, each with its numeric ID, name, whether it is scheduled, the ordered list of automation steps it is built from, its current execution status and its creation and update timestamps. Every other action needs the IDs this returns. The listing is paginated, so the agent raises the limit or advances the offset to walk large accounts.
- Get Workflow Data Returns the scraped result set of a completed workflow as a table, with headers holding the column names the workflow's automations produced and content holding one row per extracted record. A workflow that has not finished returns its current status without usable rows, so the agent checks the status field before consuming the data.
- Get Workflow Logs Returns the execution log of a workflow as a list of entries, each carrying the timestamp of the event and a description of the operation performed, such as an automation starting or input data passing between steps. Used to trace how far a run progressed and diagnose a workflow that stalled or produced no rows.
- Update Workflow Status Turns the schedule of one or more workflows on or off in a single call. Activating lets Hexomatic run a workflow on its configured schedule; deactivating leaves the workflow and its collected data intact and stops further automatic runs, which is the safe way to pause a scrape that is consuming credits.
- Delete Workflows Permanently deletes one or more workflows together with the data they collected. This cannot be undone, so Update Workflow Status is the correct action whenever the intent is to stop a workflow running rather than to remove it.
Triggers
1 triggersEvent Triggers
1- On Workflow Status Change Fires when the execution status of a workflow changes, which is how a flow reacts to a Hexomatic scrape finishing without polling for it by hand. Each cycle reads the workflow listing and emits one event per workflow whose status differs from the previous cycle, carrying the workflow ID, name, the previous and current status and the workflow's steps; a finished run reports the status completed. The trigger can be narrowed to a single workflow, and the polling interval is configurable with a minimum of 30 seconds. The first cycle records a baseline and emits nothing, so existing workflows are not replayed when the trigger is switched on.
Frequently Asked Questions
What can FlowRunner do with Hexomatic?
FlowRunner agents can run List Workflows, Get Workflow Data, and Get Workflow Logs in Hexomatic, plus 2 more actions.
Does connecting Hexomatic to FlowRunner require OAuth?
No. Hexomatic connects to FlowRunner with an API key, no OAuth flow required.
Can Hexomatic trigger a FlowRunner workflow automatically?
Yes. Hexomatic supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with Hexomatic
$100 in credits. No card required. Connect in minutes.