Press Advantage
CMS & ContentSubmit, review, and distribute press releases with Press Advantage, including agency-style management across client accounts. Agents prepare the release and hold distribution until a person signs off.
What This Integration Enables
Press Advantage is the least recallable publishing surface FlowRunner connects to. A changelog entry can be paused. A social post can be deleted. A press release goes to wire services and gets syndicated to sites you have no account on, and Get Release Pickups exists specifically to tell you afterward where all those copies landed. That asymmetry is why this connector is built around the review workflow rather than around a publish button: releases move through writing, your approval, editorial review and then distribution, and the interesting automation lives in the gaps between those states, not in the act of sending.
The other thing that shapes this integration is that Press Advantage is agency-shaped. Organizations are client businesses, releases hang off them, and one account can be running publishing programs for a dozen clients at once. FlowRunner agents work at that scale: watch every client's pipeline through one polling trigger, prepare each release with figures pulled from that client's own CRM, and route each approval to the account manager who owns the relationship. The agent handles the assembly and the chasing. The person who will have to explain a mistake to the client is the one who signs it off. That division is what Orchestration as a Service means in practice.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Milestone in the CRM becomes a release ready for approval
A funding round or a contract milestone closes in Salesforce or HubSpot. The agent resolves the client with List Organizations, then calls Order Written Release with the subject, target keyword, destination link and the client's boilerplate, so the Press Advantage writing team drafts it. On Release State Changed fires when the draft is ready. The agent pulls it with Get Release, pairs every claim in the body back to the CRM record it came from, and posts the whole package to the account manager. Approve Release Content moves it forward. Reject Release To Writers sends it back with the specific rewrite instruction, and the loop runs again without anyone opening the Press Advantage dashboard.
Multi-client publishing program monitored in one place
An agency runs recurring release programs for a dozen clients. The agent polls List Scheduled Release Orders to confirm each program is still on cadence and has a next order date, walks List Organization Releases per client to see what actually went out, and builds a single status view in Google Sheets. Where a program has stalled or a release has been sitting in an approval state longer than the agreed turnaround, the agent raises it in Slack naming the client and the release. Nothing publishes in this scenario. The value is that a program going quiet gets noticed the week it happens.
Distribution reporting back into the client pack
Once a release distributes, the agent calls Get Release Pickups for the sites that took it, with each host's page rank and whether it is indexed in Google News, and List Release Distributions for what reach was actually purchased. Both go into the client's monthly reporting pack alongside the release title and date. Where a client's pickup count is materially below their usual pattern, the agent flags it for the account manager rather than filing the report quietly, because a weak distribution is a conversation to have before the client has it with you.
Human-in-Loop Highlight
The gate sits immediately before Approve Release Content, and it exists because of what happens after. Cancel Release works right up until distribution and not one second past it: once a release is on the wire it cannot be recalled, and the syndicated copies sitting on third-party hosts do not receive your correction. So an agent that has assembled a release from a CRM record refuses to approve its own work. It posts the draft into the account manager's channel with every number in the body paired to its source, and asks: "Release 4471 for Northwind states $4.2M in Series A funding, read from opportunity 88213 on 2 August, and names Q4 as the availability date, read from the roadmap record. It is approved for 3 distribution networks. Approve to send to editorial, or return to writers?" One person confirms one figure, and the alternative to that thirty seconds is a wrong number replicating across sites you cannot edit. Approve Guideline Exception carries the same shape for a different cost: accepting it means agreeing to reduced reach on a release the client is paying for, which is a commercial decision and never an agent's to make.
Agent Capabilities
20 actionsClient Organizations
4- List Organizations Reads the client businesses on the account with their contact details, website and syndication settings. The organization IDs returned here are what the release operations expect.
- Get Organization Reads one client business with its contact details, description, social handles and whether its releases are fully syndicated to the Press Advantage homepage and public feed.
- Create Organization Sets up a new client business so releases can be published under its name. Turning homepage syndication off keeps that client's releases off the public feed.
- Update Organization Updates a client's contact details, boilerplate or syndication settings. Supply only the fields that change.
Release Submission
2- Submit Release Submits a release you wrote yourself for editorial review and distribution. The release enters an interim state, then moves through editorial approval to distribution, so follow it with Get Release or the state-change trigger rather than expecting an immediate publish.
- Order Written Release Orders a release from the Press Advantage writing team with the subject, target keyword, link and any instructions. It then moves through writing, your approval, editorial review and distribution.
Editorial Review
5- Revise Release Content Replaces the title and body of a release you wrote yourself after editors sent it back. The revised release re-enters editorial review rather than publishing.
- Approve Release Content Approves a release the writing team produced, moving it toward editorial review and distribution. An edited title and body can be supplied, in which case the release goes back through editorial review.
- Reject Release To Writers Sends a written release back with rewrite instructions instead of approving it. The release returns to the revision state until the writers resubmit.
- Approve Guideline Exception Accepts a distribution guideline exception. Press Advantage requires this when a release cannot be syndicated everywhere it normally would, and the release stays blocked until the reduced reach is accepted.
- Cancel Release Cancels a release before it is distributed. Once a release has been published to the wire it cannot be recalled, so this is a time-limited option rather than an undo.
Release Lookup
4- Get Release Reads a release with its machine-readable state, human-friendly status, title, body and any editor message. Automation should branch on the state, because the status text interpolates dates and is display only.
- List Releases Reads the releases on the account with their state, title and distribution. Press Advantage returns a bare array with no paging or filtering, so expect the full set.
- List Organization Releases Reads every release published under one client business, so a single client can be reported on without filtering the whole account.
- List Scheduled Release Orders Reads recurring release campaigns with their progress, cadence and next order date. Used to confirm an ongoing publishing program is still running on schedule.
Distribution and Reporting
3- Get Release Pickups Returns the sites that picked up a published release, with each host's page rank and whether it is indexed in Google News and supports images or retargeting. This is the payoff metric for a distribution and the same data as the release report CSV.
- List Release Distributions Returns the distribution networks attached to a release with the cost and credit type of each. Used to confirm what reach was actually bought before reporting on results.
- Add Distribution Upgrade Attaches additional distribution networks to a release to widen its reach. Supply the distribution IDs to add.
Retargeting
2- List Retargeting Pixels Reads the retargeting pixels configured on the account. Pixels can be embedded in distributed releases so readers can be retargeted afterward.
- Create Retargeting Pixel Adds a retargeting pixel for embedding in distributed releases, letting a client advertise to the people who read their coverage.
Triggers
2 triggersEvent Triggers
2- On New Release Fires when a new release appears on the account, delivering it with its title and initial state. Used to register a release against the right client program the moment it is created, whoever created it. Press Advantage publishes no webhook API, so this trigger polls and compares against the previous cycle, with a configurable interval down to 30 seconds.
- On Release State Changed Fires when a release moves to a new point in the editorial workflow, such as becoming ready for your approval or finishing distribution. Can be narrowed to a single state so the flow runs only at the moment that matters, which is what makes an approval workflow practical rather than noisy. Polls on the same configurable interval.
Frequently Asked Questions
What can FlowRunner do with Press Advantage?
FlowRunner agents can run List Organizations, Get Organization, and Create Organization in Press Advantage, plus 17 more actions.
Does connecting Press Advantage to FlowRunner require OAuth?
No. Press Advantage connects to FlowRunner with an API key, no OAuth flow required.
Can Press Advantage trigger a FlowRunner workflow automatically?
Yes. Press Advantage supports 2 triggers that can start a FlowRunner workflow automatically.
Start building with Press Advantage
$100 in credits. No card required. Connect in minutes.