DigitalPilot
Analytics & DataConnect AI agents to DigitalPilot, a cookieless B2B marketing attribution platform. Agents read attribution reports and the leads its on-site forms captured, maintain target account lists and form definitions, and manage outbound webhook subscriptions.
What This Integration Enables
DigitalPilot exists because third-party cookies stopped answering the question B2B marketers actually have, which is not "which visitor" but "which company." It identifies anonymous website visitors by organization and ties advertising spend to pipeline outcomes, and that company-level view is what makes it worth putting in a flow: an account-level signal can be routed to an account owner, whereas a session-level signal cannot be routed to anyone. FlowRunner agents pull attribution across six report shapes, covering aggregated account-level metrics with domain search and a high-intent filter, time-series totals for accounts, visitors, sessions, high-intent sessions, leads and assisted attribution, performance grouped by traffic channel, performance grouped by UTM source and medium combinations, visit and engagement metrics for target-account domains, and a paginated raw activity stream for a single company domain. Beyond reporting, agents read captured leads, read the tracked account set and add or remove domains, create, rename, and delete target-account lists, read and manage lead-capture form definitions, and manage the outbound webhook subscriptions that carry DigitalPilot's events to a URL of your choosing.
Two clarifications, because the reporting surface and the write surface are easy to confuse. On leads, Get Leads reads the leads DigitalPilot has already captured, filtered by source, free text, and date range, and requires lead capture to be enabled. The connector does not itself capture a lead; capture happens on your site through a DigitalPilot form, and Create Form and Update Form define what that form asks for. On events, this connector exposes no FlowRunner triggers. The webhook actions here register and maintain a subscription that delivers high-intent, target-account, and lead-capture events to an external endpoint you specify, optionally signed with an X-DigitalPilot-Signature header, and Send Webhook Test Delivery posts a sample payload to a URL so you can prove the endpoint works before you rely on it. Nothing in DigitalPilot starts a FlowRunner flow. Change detection is a scheduled poll of the report and activity operations. The API key is tag-scoped, so one connection maps to one DigitalPilot workspace. The connector is built and verified against DigitalPilot's official API.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A Named Account Moves and Sales Hears About It
An account-based programme has a list of target domains. On a schedule, the agent calls Get Target Account Visits for the list to see which domains have engagement above their usual level, then calls Get Domain Activities for each mover to pull the raw activity stream, which pages they read and in what order. It calls Get Channel Report to establish how they arrived. It posts to the account owner in Slack with the company, the page sequence, the channel, and a link to the record in HubSpot. The signal reaches the person who can act on it while the visit is still recent, rather than appearing in a monthly deck.
Spend Reviewed Against Pipeline, Not Against Clicks
A weekly flow calls Get Dashboard Report for the time series of accounts, visitors, sessions, high-intent sessions, leads, and assisted attribution, then calls Get Channel Report and Get UTM Report to break the same period down by channel and by source and medium combination. It joins that against campaign spend pulled from Google Ads and writes the combined view into a reporting sheet in Google Sheets. The conversation with finance changes shape, because the cost per identified account is on the same row as the cost per click.
The Target List Maintained From Live Signal
New logos in the target market appear and old ones stop mattering. The agent calls Get Overview Report with the high-intent-only filter to find companies engaging repeatedly that are not yet tracked, checks them against Get Target Accounts, and assembles a proposal. It calls Get Target Account Lists to see which list each candidate belongs in. Where a domain clearly qualifies against an agreed rule, it calls Add Target Account. Where a tracked domain has shown nothing for a long period, it assembles the removal candidates and sends them for review rather than calling Remove Target Account on its own judgement.
Human-in-Loop Highlight
A target account list is not a report filter, it is the definition of who counts. Every high-intent alert, every account-level visit metric, and every webhook subscribed to target-account events resolves against that list, which means Delete Target Account List and Remove Target Account do not produce an error anywhere, they produce silence. Delete a list and the domains in it stop generating alerts, the account owners stop hearing about their accounts, and nothing in any downstream system reports a failure, because from every consumer's point of view those companies simply stopped visiting. That failure mode is worse than a loud one: an alerting pipeline that has quietly stopped alerting looks exactly like a quiet quarter. So the agent proposes and a person decides. Before any Delete Target Account List or any batch of Remove Target Account calls, it calls Get Target Accounts to enumerate the domains affected, calls Get Target Account Visits for each to show what would stop being watched, and calls List Webhooks to name the subscriptions that carry target-account events onward. It posts to the programme owner: "Proposed removal from tracking: [n] domains across list [name]. Combined visits in the last [period]: [n], of which [n] were high intent. Webhook subscriptions currently carrying target-account events: [list and their destination URLs]. Deleting this list stops alerting for these domains and returns no error to any consumer. Approve, narrow, or cancel?" The owner decides. Reading reports, pulling activity streams, and routing a visit to an account owner all run unattended, because none of them change what the system watches. Changing the definition of a named account programme is human-in-the-loop work, and Send Webhook Test Delivery is how the agent proves a replacement destination works before the old one is retired.
Agent Capabilities
24 actionsReports
6- Get Overview Report Returns aggregated account-level metrics covering companies, visitors, sessions, high intent, and channels, with pagination, domain search, and a high-intent-only filter. Used to find engaged companies that are not yet on a target list.
- Get Dashboard Report Returns time-series metrics and totals for accounts, visitors, sessions, high-intent sessions, leads, and assisted attribution. Used as the period-over-period view a marketing lead reads.
- Get Channel Report Returns performance metrics grouped by traffic channel, with an optional single-channel filter and pagination. Used to attribute account movement to how those accounts arrived.
- Get UTM Report Returns performance metrics grouped by UTM source and medium combinations. Used to compare campaigns at the level the tagging was actually built at.
- Get Target Account Visits Returns visit and engagement metrics for target-account domains, optionally filtered by channel and by list. This is the operation that tells an agent which named accounts moved.
- Get Domain Activities Returns a paginated raw activity stream for a single company domain. Used to turn "this account is engaged" into the specific page sequence an account owner can act on.
Leads
1- Get Leads Returns the leads DigitalPilot has captured for the tag, filtered by source, free-text search, and date range. Requires lead capture to be enabled. This reads captured leads; capture itself happens on your site through a DigitalPilot form.
Target Accounts
3- Get Target Accounts Lists tracked company domains, either across all lists or within a specific list.
- Add Target Account Adds a company domain to the default list or to a specific list. Used to bring a qualifying account into the tracked set from live signal.
- Remove Target Account Removes a company domain from a specific list. Removal is silent from every consumer's point of view, so it belongs behind a review step.
Target Account Lists
4- Get Target Account Lists Returns all target-account lists for the tag. Used to resolve which list a candidate domain belongs in.
- Create Target Account List Creates a new named list. Used when a new programme, region, or segment needs its own tracked set.
- Update Target Account List Renames an existing list.
- Delete Target Account List Deletes a list. Every domain in it stops generating target-account signal, and no downstream consumer receives an error.
Forms
5- List Forms Returns the lead-capture forms defined for the tag.
- Get Form Retrieves the full definition of a single form, including its fields.
- Create Form Creates a lead-capture form with a title and fields. This defines what a form asks visitors for; it does not capture a lead by itself.
- Update Form Updates a form's title and fields. Changing fields changes what every subsequent submission contains, so downstream mappings should be checked alongside it.
- Delete Form Deletes a form.
Webhooks
5- List Webhooks Returns the configured outbound webhooks and their event subscriptions, including their destination URLs.
- Create Webhook Registers a webhook subscribed to high-intent, target-account, and/or lead-capture events, delivering to an external endpoint you specify. This creates a DigitalPilot subscription to a URL of your choosing; it does not create a FlowRunner trigger.
- Update Webhook Changes a webhook's event subscriptions. A narrowed subscription stops delivery silently, so pair it with a test delivery.
- Delete Webhook Deletes a webhook by ID or by URL.
- Send Webhook Test Delivery Posts a sample event payload to a URL, optionally signed with an `X-DigitalPilot-Signature` header. This is the rehearsal that proves a destination works before a live subscription is pointed at it.
Frequently Asked Questions
What can FlowRunner do with DigitalPilot?
FlowRunner agents can run Get Overview Report, Get Dashboard Report, and Get Channel Report in DigitalPilot, plus 21 more actions.
Does connecting DigitalPilot to FlowRunner require OAuth?
No. DigitalPilot connects to FlowRunner with an API key, no OAuth flow required.
Can DigitalPilot trigger a FlowRunner workflow automatically?
DigitalPilot doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with DigitalPilot
$100 in credits. No card required. Connect in minutes.