Proofly
AdvertisingManage social proof notification widgets with Proofly, reading usage, listing campaigns, switching them on or off, and pulling captured leads. Agents surface genuine recent activity on the site.
What This Integration Enables
Proofly is the supervision side of social proof rather than the publishing side. There is no push-an-event call here; what the API gives an agent is the ability to see what is actually running, how it is performing and what it has collected, and to switch a campaign off. That matters because the failure mode of a social proof widget is not a crash, it is silence: it keeps running, correctly, through a stockout, a price change, a site outage, a rebrand and a support incident, advertising a version of the business that stopped being true weeks ago. Agents read the account and its impression usage, list every campaign and the notifications inside it with their URL triggers and display configuration, compare that against what the business is currently doing, flip a campaign inactive when the two disagree, and pull the raw records a lead-collector notification has captured so they land in a system that someone actually works from. The connector turns a widget nobody watches into one that reports to a flow.
Without FlowRunner
With FlowRunner
Use Case Scenarios
A morning report on what the widget is doing
Each morning a flow calls List Campaigns for every campaign in the account, then List Campaign Notifications for each one, and assembles a single view: which campaigns are enabled, which domains they target, and per notification the impressions, hovers, clicks and leads it has produced. Get Account adds the current period's impression total against the plan. The digest goes to Slack with the notifications whose click rate has dropped since the last run called out at the top. The point is not the dashboard, which already exists. The point is that somebody now reads it every day without having to remember to.
The site changes and the widget hears about it
A product sells out, a promotion ends, or the status page reports an incident. The agent identifies the campaigns whose target domain and URL rules put notifications on the affected pages and proposes taking them dark. Once a person confirms, Toggle Campaign switches the campaign and every notification inside it off in one call. When the situation clears, the same flow proposes the reverse. Social proof for a page that cannot fulfil is worse than no social proof, and the gap between the site knowing and the widget knowing is usually measured in whoever is on shift.
Captured leads land where the team works
A lead-collector notification has been quietly gathering email addresses. Get Notification Data returns the raw records, each with the captured payload, the visitor IP address, the page URL, a resolved city, country code and country name, and a timestamp. The agent creates or updates the corresponding contact in HubSpot with the page that produced the lead as the source, and appends the run to Google Sheets for reconciliation. These records are personal data with location attached, so the flow writes only the fields the CRM has a stated purpose for and logs what it moved.
Human-in-Loop Highlight
Toggle Campaign does not take a value. It inverts whatever state the campaign is currently in, which means an agent acting on a stale reading does the exact opposite of what it intended: a campaign a human deliberately switched off during an incident gets switched back on by a flow that thought it was turning it off. So the gate sits precisely there. Before any flip, the agent calls List Campaigns to read the live enabled state, and if that state does not match the state its last approved run recorded, it refuses to call Toggle Campaign and asks instead: "Campaign Homepage Purchases is currently ENABLED. My last run left it DISABLED, so someone changed it outside this flow. Calling Toggle now would disable it. Proceed, skip, or re-read?" The message goes to the campaign owner in Slack with the campaign name, both states and the timestamp of the last approved run. That disagreement is an automation exception in the strict sense: not an error, just a fact the agent is not entitled to resolve on its own. FlowRunner's human-in-the-loop gate exists so the agent can stop cleanly at that line instead of guessing and being right most of the time.
Agent Capabilities
6 actionsAccount and Audit
2- Get Account Returns the account behind the API key with its name and email, lifetime and current-period impression totals, login and registration metadata, and the pixel key and debug flag the on-site widget uses. Used as a connection check and to report impression usage against plan limits before a traffic spike.
- Get Activity Log Returns the account activity log as entries carrying an event type such as login.success or register.success, with the originating IP address and timestamp. Used to monitor who is getting into the account and to feed a security audit flow.
Campaign Supervision
3- List Campaigns Lists every social proof campaign with its numeric ID, name, target domain and subdomain setting, enabled state and creation date. The campaign ID it returns is what List Campaign Notifications and Toggle Campaign require, and the enabled state is what a supervision flow compares against its own record.
- List Campaign Notifications Returns every notification inside one campaign with its type, URL trigger rules, display configuration including position, duration and mobile handling, and a stats block carrying impressions, hovers, clicks and leads. Used to find notifications pointing at pages that no longer exist and to spot performance that has quietly fallen off.
- Toggle Campaign Flips a campaign between active and inactive, switching all of its notifications on or off in one call. The endpoint toggles the current state rather than accepting an explicit value, so read the campaign with List Campaigns first to know which way it will move. Returns a confirmation stating whether the campaign was enabled or disabled.
Captured Data
1- Get Notification Data Returns the raw records a single notification has captured, such as the email addresses submitted to a lead collector. Each record carries the captured payload, the visitor IP address, the page URL, a resolved city, country code and country name, and a timestamp. Use List Campaign Notifications to obtain the notification ID first.
Frequently Asked Questions
What can FlowRunner do with Proofly?
FlowRunner agents can run Get Account, Get Activity Log, and List Campaigns in Proofly, plus 3 more actions.
Does connecting Proofly to FlowRunner require OAuth?
No. Proofly connects to FlowRunner with an API key, no OAuth flow required.
Can Proofly trigger a FlowRunner workflow automatically?
Proofly doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Proofly
$100 in credits. No card required. Connect in minutes.