FlowRunner
PricingContact
Theme
Start Free

Audiense Insights

Analytics & Data

Connect AI agents to Audiense Insights, a social audience intelligence platform. Agents read audience reports and their status, pull segment insights, influencer lists, and baseline comparisons, and read the content those audiences engage with, all across a read-only surface.

6 actions Custom auth available
A scheduled poll runs, or a campaign planning flow reaches its audience research step
List Reports returns the account's reports with their status, so the flow knows which are ready
Get Report returns a ready report's segments, full audience size, and segmentation type
Get Audience Insights returns the demographic, behavioural, and psychographic distributions
Compare Influencers returns influencers scored against a chosen baseline from List Baselines
The strategist receives the segment profile with the influencer shortlist and its baseline
Strategist approves who gets contacted and what leaves the company before anything is sent

What This Integration Enables

Audiense Insights does something most analytics tools do not: it segments an audience and then tells you how each segment differs from a baseline, which is the difference between a description and a finding. An influencer with high affinity in your audience is not interesting until you know the affinity against a general population baseline, and that is what Compare Influencers returns alongside a uniqueness score. This connector brings that comparison into a flow so the research reaches the people writing the plan rather than sitting in a tab. FlowRunner agents list the account's reports with their status and segmentation type, retrieve a report's segments, full audience size, sharing visibility, and access links, pull statistical distributions across demographics, behaviour, psychographics, and socioeconomics for a chosen audience, compare an audience's influencers against a baseline with pagination and filtering by bio keyword, entity type, follower range, categories, and countries, read the liked, shared, and influential content an audience engages with, and list the predefined baseline audiences available as comparison points.

Two things need saying plainly, because a connector page that overstates them is worse than useless. Every operation here is read-only. This connector cannot create, launch, or refresh a report; reports are built in Audiense, and the flow reads what exists. Its List Reports and Get Report operations return status, which is what lets an agent poll for a report that a person started and act when it becomes ready. And there are no triggers. Nothing in Audiense starts a FlowRunner flow, so the pattern is a scheduled List Reports poll that checks status, or a flow started by whatever else in your stack marks the beginning of a campaign cycle. IDs for insights, influencers, and content come from the segments and full audience returned by Get Report, so Get Report is almost always the second call in the chain. Baselines are a fixed platform-provided list and List Baselines does not require a report. The connector is built and verified against Audiense's official API.

Without FlowRunner

Research read once and forgotten A report is opened in the platform during planning and never referenced again
Influencer lists compared by eye Affinity numbers are read off a screen without the baseline that gives them meaning
Reports shared by forwarding a link An access link goes out to a client with whatever visibility the report already carries

With FlowRunner

Research pulled into the flow that uses it Segment distributions arrive inside the brief the strategist is actually writing
Influencers ranked against a stated baseline Affinity, baseline affinity, and uniqueness travel together so the number can be argued with
Outbound sharing is a decision What leaves the company is chosen by a person, not produced by a step in a flow

Use Case Scenarios

A Brief That Arrives With Its Evidence

A campaign cycle begins and a strategist needs the audience picture. The agent calls List Reports to find the current report for the brand, calls Get Report to pull its segments and full audience size, and calls Get Audience Insights for each segment that exceeds a size threshold, filtering by the insight names the brief actually needs rather than pulling everything. It assembles the distributions into a structured brief and writes it into the planning document in Notion. The strategist opens a brief with the segment profiles already in it, and spends the hour on the argument instead of on the export.

Polling for a Report Somebody Started

Audience reports take time to build, and the person who started one does not want to keep checking. The agent polls List Reports on a schedule and reads the status of the reports it is watching. When a report moves to ready, it calls Get Report to pull the segment structure, calls Get Audience Content to see the posts, domains, hashtags, and media the audience actually engages with, and posts a summary to the requester in Slack with the report title and the top content themes. The research lands the moment it exists rather than the next time somebody remembers to look.

An Influencer Shortlist With Its Baseline Attached

A partnership team needs candidates for a campaign. The agent calls List Baselines to select the comparison population, filtering by country where the campaign is regional, then calls Compare Influencers for the target segment with filters on follower range, categories, countries, and bio keyword to keep the list relevant. It pages through the results and assembles a shortlist that carries affinity, baseline affinity, and uniqueness for every name, because an influencer who is popular everywhere is not the same finding as one who is disproportionately present in this audience. The shortlist goes to the partnership lead as a ranked table with the baseline named at the top of it.

Human-in-Loop Highlight

A read-only connector cannot break anything inside Audiense, so pretending otherwise would be theatre. The consequential moment sits one system downstream, and Get Report points straight at it, because what Get Report returns alongside the segments is the report's sharing visibility and its access links. An access link carries the report's own visibility, not the recipient's, which means forwarding one to a client, an agency partner, or a prospective sponsor shares whatever that report is configured to share, including segments and audience sizes the account never intended to publish outside the company. The same applies to a Compare Influencers shortlist: the moment it stops being research and becomes a list of named people who are going to be contacted and paid, it is a commitment with a budget attached. So the agent assembles and stops. It posts to the campaign owner: "Audience research ready for [report title]. [n] segments, full audience [size], baseline [name]. Influencer shortlist: [n] names, affinity range [x] to [y] against baseline affinity [z]. Report sharing visibility is currently [value]. Requested recipients: [list, with which are outside the company]. Approve the shortlist and confirm what is shared externally?" The owner approves the names and the recipients. Reading distributions, polling for status, and building the brief all run unattended, because none of it leaves the building. Deciding who gets contacted, and what crosses the company boundary, is human-in-the-loop work.

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

Reports

2
  • List Reports Lists the intelligence reports owned by the account with their id, title, segmentation type, creation date, and status. Because there are no triggers, this is the polling surface an agent uses to wait for a report somebody started to become ready.
  • Get Report Retrieves a report's status, segmentation type, full-audience size, segments, sharing visibility, and access links. This is the call that yields the segment and audience IDs every other operation needs, and it is where an agent learns what a report would expose if its link were forwarded.

Insights

1
  • Get Audience Insights Returns statistical distributions for an audience across demographics, behaviour, psychographics, and socioeconomics, optionally filtered by insight name. Used to build a segment profile without pulling every distribution the platform holds.

Influencers

1
  • Compare Influencers Retrieves an audience's influencers compared against a baseline audience, returning affinity, baseline affinity, and uniqueness scores. Supports pagination and filtering by bio keyword, entity type, follower range, categories, and countries.

Content

1
  • Get Audience Content Returns the liked, shared, and influential content an audience engages with, including popular posts, top domains, emojis, hashtags, links, media, and a word cloud. Used to ground creative direction in what the audience actually shares.

Baselines

1
  • List Baselines Returns the predefined baseline audiences available for comparison, with label, id, country, and gender, optionally filtered by country. Baselines are a fixed platform-provided list and this call does not require a report.

Frequently Asked Questions

What can FlowRunner do with Audiense Insights?

FlowRunner agents can run List Reports, Get Report, and Get Audience Insights in Audiense Insights, plus 3 more actions.

Does connecting Audiense Insights to FlowRunner require OAuth?

Audiense Insights uses a custom authentication method to connect to FlowRunner.

Can Audiense Insights trigger a FlowRunner workflow automatically?

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

Start building with Audiense Insights

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