FlowRunner
PricingContact
Theme
Start Free

ProvenExpert

Loyalty & Referral

Read profiles and aggregated review summaries on ProvenExpert, the German review and rating platform, and work the inbound customer requests and leads they generate. Agents route new reviews and review-sourced leads to an owner.

16 actions Session available
A scheduled poll calls List Customer Requests for enquiries that arrived overnight
Agent reads the requester's name, contact details, message, requested industry and location, and the due date
Agent calls List Profile Leads to see whether the enquiry has already been read or answered by someone
Agent resolves the free-text industry label against List Industries and matches it to the right profile
Agent creates the enquiry as a record in your CRM with the due date carried across
Agent alerts the owning rep with the message, the location and how long is left on the clock
The rep decides whether to pursue the enquiry or let it lapse, and the agent records the call either way

What This Integration Enables

ProvenExpert is a German review and rating platform, and treating it purely as a source of stars misreads what it does. Half of this connector is reputation data: profiles, aggregated review summaries, recommendation rates, and the split between reviews collected on the platform and ratings pulled in from external sources. The other half is demand. Customer requests arrive through contact forms and the Expert Compass matching service, become leads routed to specific companies, and carry a due date and an unlock counter. That second half means ProvenExpert behaves like a lead source that happens to be attached to a review site, and lead sources reward speed.

FlowRunner agents work both halves through connectors built and verified against the ProvenExpert API. On the reputation side, an agent reads Get Review Summary for the numbers that drive a rating badge or a monthly report, and Get Public Profile for the subset ProvenExpert exposes publicly when you are syndicating a rating onto your own site. On the demand side, an agent polls inbound customer requests, matches them to the right profile by resolving the industry taxonomy, pushes them into the CRM before the due date becomes a problem, and tracks whether each lead has been read and answered. Note one boundary honestly: this connector reads reviews and works requests, leads and referrals. It does not post reviews or replies, so the reputation work an agent does here is routing and reporting, not publishing.

Without FlowRunner

Enquiries sit in a second inbox Requests arrive in a platform nobody has open next to the CRM
Due dates discovered late The clock on an enquiry is only noticed when it has nearly run out
Rating data pulled by hand Review counts and scores are copied into decks and site badges manually

With FlowRunner

Enquiries land where reps work Each request becomes a CRM record with the message and due date attached
The clock is visible from the start The owning rep is alerted with the time remaining, not after the fact
Rating data read from source Review counts, scores and recommendation rates are pulled live when they are needed

Use Case Scenarios

Inbound enquiries routed before the clock runs down

Requests submitted through a contact form or Expert Compass carry a due date, and a due date is only useful to whoever can see it. A scheduled flow calls List Customer Requests filtered by status, reads each requester's message, industry and location, checks List Profile Leads to confirm nobody has already answered, resolves the industry against List Industries, and creates the enquiry in your CRM with the deadline carried across. The owning rep is alerted with the message text and the time remaining rather than a bare notification that something arrived.

Rating figures that stay current wherever they are shown

Get Review Summary returns the numbers people actually put on a site: total review count and score, the internal review count, the number and average score of external ratings pulled in from other services, how many external sources are currently inactive, the recommendation count and rate, and the timestamp of the most recent review. A scheduled agent pulls these per profile, writes them into Google Sheets for the monthly report, and posts to the marketing channel when the average score moves or when an external rating source goes inactive, which is the failure mode that silently degrades a badge nobody is watching.

Multi-location reputation reporting

A business with several branches holds several profiles. The agent calls List Profiles, narrowed by country or creation window, then loops Get Profile for the detail the list omits, including awards, external rating sources and opening hours. It pairs each profile with Get Current Monthly Statistics for live lead-unlock usage this month and List Monthly Statistics for the trend, and produces one table showing which locations are collecting reviews, which are converting enquiries, and which are quietly doing neither.

Human-in-Loop Highlight

Create Referral is the operation on this connector that reaches a stranger. A reviewer recommends the business to a friend and hands over that friend's name, email address and phone number, and Create Referral causes ProvenExpert to generate an invitation and reach out to invite them to review the business. The referred person never gave you their address. They gave it to nobody; a third party gave it on their behalf. That is why the action carries consent flags mirroring what the referring reviewer agreed to, and why an agent that fires it on every inbound recommendation is making a data-protection decision it has no standing to make, in the market where that decision is least forgiving. So the agent stops before the invitation goes out. It posts to the marketing owner: "Referral submitted by a reviewer on the Munich profile. Referred person is Thomas Berger, with an email and phone number supplied. The consent flags on the submission are set for contact but not for phone. List Referrals shows no existing invitation to this address. Create the referral and send the invitation, create it without the phone number, or discard?" The owner decides. Everything upstream of that point, the reading, matching, counting and reporting, runs without anyone in the way.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via email
Human decides
Agent resumes with decision

Agent Capabilities

16 actions

Profiles

3
  • List Profiles List the ProvenExpert profiles the authenticated account can access, each with its short profile ID, slug, title, industry, contact data, opening hours, websites, social media profiles and status. Paginated and narrowable to a country or a creation-date window. The starting point for any reporting flow that needs profile IDs.
  • Get Profile Fetch one profile by resource ID with the full record, including description, offers and activities text, awards, external rating sources, geo location, opening hours and inherited profile settings. Used when the list view does not carry enough detail.
  • Get Public Profile Return the publicly visible representation of a profile, the subset ProvenExpert exposes on the public profile page. Used when syndicating a company's rating and contact details onto your own website.

Reviews

1
  • Get Review Summary Return the aggregated rating figures for a profile: total review count and score, the internal review count, the number and average score of external ratings pulled in from other review services, how many external sources are inactive, the recommendation count and rate, and the timestamp of the most recent review. The endpoint behind rating badges and social proof widgets.

Customer Requests

3
  • List Customer Requests List inbound customer requests, meaning enquiries submitted through a ProvenExpert contact form or the Expert Compass matching service, each with the requester's name, email address and phone number, the message, the requested industry and location, and the due date. Filterable by status, approval method or approval state to build a follow-up queue.
  • Get Customer Request Fetch a single customer request by resource ID with the requester's contact details, message, requested industry and location, due date and creation timestamp.
  • Create Customer Request Submit a new customer request into ProvenExpert, handing an enquiry captured on your own site over to the platform. Choose Contact Form when the enquiry targets a specific company, or Expert Compass when ProvenExpert should match it to suitable providers by industry and location.

Leads

2
  • List Profile Leads List the leads generated for profiles, where a lead is a customer request routed to a specific company. Each reports its status and classification, whether it has been read, answered, unlocked or notified, when it was answered, and the name and message from the originating request. Filterable by profile, status or originating request.
  • Get Profile Lead Fetch a single lead by resource ID with its status, classification, read, answered and unlocked flags, the originating customer request reference and the message text.

Referrals

4
  • List Referrals List the referrals recorded against the account, meaning people a reviewer has recommended the business to, each with the referred person's name, email address, phone number and comment, the invitation URL generated for them, and whether the referral has been reported back to the customer.
  • Get Referral Fetch one referral by resource ID with the referred person's details, the generated invitation URL, the linked review ID, the consent flags and whether it has been reported back.
  • Create Referral Record a new referral so ProvenExpert can invite the referred person to review the business. First name, last name and email address are required, the optional consent flags mirror what the referring reviewer agreed to, and ProvenExpert returns the invitation URL. The operation that should always carry an approval gate.
  • Count Referrals By Profile Return how many referrals have been recorded for a profile. Used for dashboards and thresholds without paging the whole collection.

Statistics

2
  • List Monthly Statistics List the per-month statistics rows recorded for profiles, each carrying the profile reference, the month and the lead unlock counter for that month. Filterable by profile or month to assemble a time series.
  • Get Current Monthly Statistics Return the statistics row for the month currently in progress for a profile, without needing its month key. Used for live usage dashboards showing how many leads have been unlocked so far.

Reference Data

1
  • List Industries List the industry taxonomy ProvenExpert uses to categorise profiles and route customer requests, each entry with its internal name, localised title, parent industry and search aliases. Used to resolve a free-text industry label to the identifier the platform expects.

Frequently Asked Questions

What can FlowRunner do with ProvenExpert?

FlowRunner agents can run List Profiles, Get Profile, and Get Public Profile in ProvenExpert, plus 13 more actions.

Does connecting ProvenExpert to FlowRunner require OAuth?

No. ProvenExpert connects to FlowRunner with session-based authentication, no OAuth flow required.

Can ProvenExpert trigger a FlowRunner workflow automatically?

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

Start building with ProvenExpert

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