FlowRunner
PricingContact
Theme
Start Free

Birdeye

Social Media

Manage your Birdeye reputation pipeline. Agents pull reviews collected across Google, Facebook, and other connected sites, send review requests over email or SMS after a purchase or appointment, and keep the customer list in sync.

5 actions API key available
Birdeye website ↗ Platform Documentation ↗ Capability data verified 2026-07-28
An order is fulfilled in the storefront, marking the service moment complete
Add Customer writes the buyer into the Birdeye location with email and phone
The agent checks the support system for open tickets tied to that customer
Customers with an open complaint route to the location manager, who decides whether asking for a review right now is wise
Send Review Request invites the cleared customers over email or SMS
List Reviews sweeps for new reviews on the next scheduled run
New low-rating reviews post to the operations channel with reviewer, rating, and source

What This Integration Enables

Reputation is a pipeline, not a scoreboard. The businesses with strong review profiles are not luckier; they ask consistently, ask at the right moment, and respond to problems before the internet reads them. All three behaviors are operational habits, which means all three can be orchestrated. This connector gives FlowRunner agents the levers of that pipeline: the customer list, the request, and the monitoring sweep, all scoped to a Birdeye business location. - Send review requests over email or SMS the moment a purchase, appointment, or service completes - Sync customers from CRMs, forms, and stores into Birdeye so campaigns target a live list, not an export - Pull reviews collected across Google, Facebook, and other connected sites for monitoring and reporting - Report aggregate reputation metrics, average rating and review count, into dashboards the team actually reads - Run the same flows per location for multi-site operators, scoped by Business ID Everything is scoped to a Birdeye business location, set once on the service or overridden per call, which is what makes this workable for multi-location operators: the same flow runs per location, each with its own customer list, request stream, and reputation metrics, without anyone maintaining per-location logic. The one operation that touches customers directly, Send Review Request, is exactly where FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) gate earns its place.

Without FlowRunner

Reviews solicited by mood Requests go out when someone remembers, usually to whoever is top of mind, not top of experience
Bad timing, worse reviews The request lands while the customer's support ticket is still open, and the review reflects it
Reputation checked monthly Someone reads the Google listing when a bad review has already sat public for two weeks

With FlowRunner

Every service moment asks Fulfillment, appointment, or project close triggers the request while the experience is fresh
The angry customer is not asked Open complaints route to a person before any request sends, by design
Low ratings surface in hours Agents sweep List Reviews on a schedule and alert the team the day a low rating appears

Use Case Scenarios

The post-purchase ask, timed and filtered

A [Shopify](/integrations/shopify) order is fulfilled. The agent calls Add Customer with the buyer's name, email, and phone, waits the configured settling period, then checks for open support conversations. Clean customers get Send Review Request; anyone mid-complaint routes to the manager first. The request goes out while the delivery is still on the doorstep, which is when people actually write reviews. Because Birdeye merges duplicate contacts on email and phone, the enrollment step is safe to re-run, and a customer who orders twice does not become two records asking twice.

Low ratings become same-day operations work

Every morning, the agent runs List Reviews sorted newest first, logs each new review to [Google Sheets](/integrations/google-sheets), and posts anything at or below three stars to [Slack](/integrations/slack) with the reviewer name, comment, and source site. The location manager responds within the day instead of discovering the review during a monthly check. Get Business runs weekly to chart average rating and review count over time, so the team sees the trend, not just the incidents. Across multiple locations, the same sweep runs per Business ID, and the weekly report ranks locations by rating movement, which is how a regional manager learns where to spend Tuesday.

The CRM audience becomes a review engine

Marketing wants reviews from the long tail of past customers, not just last week's. The agent pulls contacts from [HubSpot](/integrations/hubspot), syncs them into Birdeye with Add Customer, relying on Birdeye's merge-by-email behavior to avoid duplicates, and proposes a request batch segmented by last service date. The batch size and segment go to the marketing lead for approval before Send Review Request runs, because a thousand simultaneous SMS messages is a decision, not a default. The long tail converts at whatever rate it converts; what matters is that the asking finally happened, systematically, without a campaign project.

Human-in-Loop Highlight

Send Review Request puts words in front of a real customer on their phone or in their inbox, and it cannot be unsent. Ask at the wrong moment, while a complaint is open, after a botched delivery, twice in one week, and the request does not just fail, it manufactures the negative review it was meant to prevent. So FlowRunner agents divide the work: the agent handles enrollment, timing, and dedup at machine speed, and two situations always pause for a person. A customer with any open support activity routes to the location manager with the ticket context attached. And any batch above a per-run threshold posts its segment, size, and channel mix for approval before a single message sends. The routine ask runs itself; the risky ask waits for judgment.

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

5 actions

Reviews

2
  • List Reviews Retrieves reviews collected for a business location across connected review sites, with reviewer name, rating, comment, source, and timestamp. Pages via count and start offset, and sorts by date or rating. The monitoring sweep behind alerting and reporting.
  • Send Review Request Sends a review invitation to a customer over email and/or SMS, given a name and at least one contact channel. The customer-facing write this page's human gate governs.

Customers

2
  • Add Customer Adds a customer to a business location so review requests and campaigns can target them. Birdeye typically merges duplicates on email or phone, which makes this safe to call from sync loops.
  • List Customers Retrieves the customers associated with a location, with names and contact details, paged by count and start offset. The audit view of who the campaigns can reach.

Business

1
  • Get Business Retrieves a location's profile: name, address, phone, category, and aggregate metrics including average rating and review count. The source for reputation trend reporting.

Frequently Asked Questions

What can FlowRunner do with Birdeye?

FlowRunner agents can run List Reviews, Send Review Request, and Add Customer in Birdeye, plus 2 more actions.

Does connecting Birdeye to FlowRunner require OAuth?

No. Birdeye connects to FlowRunner with an API key, no OAuth flow required.

Can Birdeye trigger a FlowRunner workflow automatically?

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

Start building with Birdeye

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