Feedier
FormsFeedier is a French customer feedback and experience management platform that pulls in surveys, reviews, email, SMS, chat and call center feedback and enriches it with AI topics and sentiment. Agents query feedback with FQL segments, read surveys, manage users and invitations, add recipients to push campaigns, and react to new feedback.
What This Integration Enables
Feedier is not a survey tool with a dashboard bolted on. It treats feedback as a governed data set: every record carries attributes, AI detected topics and sentiment, it is sliced with a query language of its own, and it can be assigned to a named owner and moved through close the loop statuses. That design only pays off if something acts on the records quickly, which is exactly the work an agent should own. FlowRunner agents push feedback in from channels Feedier does not collect itself, enrich records with attributes and referential lookups, assign owners, and drive the reporting and invitation cycles on a schedule.
The platform is French, which matters to buyers who need their experience data held in the EU, and the connector covers both of its live APIs so the older invitation and suppression routes stay usable. What it does not do is decide anything on a customer's behalf. Agents triage, summarize and route; the reply and the remedy stay with a person, which is the human-in-the-loop default FlowRunner ships with rather than a policy you have to configure.
Without FlowRunner
With FlowRunner
Use Case Scenarios
-
A detractor becomes a ticket with an owner, not a chart
On New Feedback fires for a record matching a filter written in Feedier's query language. The agent calls Get Feedback, reads the free text and the AI topics, and decides which team owns the issue. It writes that decision back with Attach Feedback Attributes so the routing is visible on the record, calls Attach Feedback Owners to name the responsible person, and opens a ticket in Zendesk or Linear with the summary. Update Feedback Status moves the record to contacted, then to resolved when the ticket closes. The customer gets a person, and the record shows who it was.
-
The invitation that follows the event, not the calendar
An order ships in Shopify or a payment settles in Stripe. Rather than waiting for a monthly send, the agent calls Send Email Invitation or Send SMS Invitation immediately, carrying the order number, store and product as custom fields so the answers arrive already segmented. Reviews collected elsewhere, on Trustpilot or an app store, are normalized and pushed in with Submit Feedback under their own source, using a stable fingerprint so a re-run cannot duplicate them. Once a week, Evaluate KPI Formula and Create Report Share Link produce a figure and a public link that post to Slack.
-
The retention purge that pauses for a signature
A data retention policy says feedback older than a defined period leaves the platform. The agent assembles the query expression, runs List Feedback against it, and reports what the expression actually matches: the count, the date range, the sources and a sample of records. Then it stops. Only after the data owner confirms the expression does it call Delete Feedback, and it reports back the matched, deleted and remaining counts so the run can be repeated safely to completion.
Human-in-Loop Highlight
Delete Feedback is the one operation on this connector that cannot be walked back. It takes a query expression rather than a list of identifiers, so a filter that is one clause too loose deletes far more than anyone intended, and Feedier keeps the deleted fingerprints reserved, which means the same submissions cannot simply be pushed back in afterward. Restoring from a backup is not on the table. So the purge agent never runs the expression it built. It runs the read first and posts: "This expression matches 12,480 records across four sources, the newest submitted eleven days ago. The policy says twenty four months. Confirm the expression, or send back a corrected one." The data owner answers in Slack. Assembling and testing the query is machine work. Signing off on which customer feedback stops existing is not.
Agent Capabilities
61 actionsFeedback
11- List Feedback Lists feedback records, filtered with a query language expression. Paged by cursor rather than page number, so a flow feeds the previous response's cursor back in to continue.
- Get Feedback Reads one record in full, including answers, attributes, owners, AI topics and sentiment.
- Submit Feedback Pushes a record into Feedier from a channel it does not collect itself, such as a review site, a call transcript or a proprietary app. Idempotent through a fingerprint, so replays never create duplicates.
- Update Feedback Status Moves one record through the close the loop statuses. The step that makes progress on a customer issue visible inside Feedier rather than only in the ticketing system.
- Bulk Update Feedback Status Moves every record matching an expression. Runs inline for a small match and as a background job beyond that, so read the async flag before treating the count as work already done.
- Delete Feedback Permanently deletes the records matching an expression, up to a per call limit, and reports matched, deleted and remaining. Deleted fingerprints stay reserved. The operation this page's human gate exists for.
- Attach Feedback Attributes Adds attributes to matching records. It adds rather than overwrites, so attaching a name a record already carries leaves a second value beside the first.
- Update Feedback Attributes Overwrites attribute values on matching records. The action to use when an enrichment pass should correct rather than accumulate.
- Detach Feedback Attributes Removes attributes from matching records.
- Attach Feedback Owners Assigns one or more Feedier users as owners of the matching records. The step that turns a bad answer into somebody's responsibility.
- Detach Feedback Owner Removes an owner from a record, for example when a ticket is reassigned.
Reports
6- List Reports Lists the reports in the account.
- Get Report Reads one report's configuration and components.
- Create Report Creates a report, optionally prefilled from surveys. Prefilled reports build their components in the background, so an immediately following read can show an empty report.
- Update Report Updates a report, which is how a monthly cycle rolls a report's global filter forward instead of rebuilding it.
- Delete Report Deletes a report and its configuration.
- Create Report Share Link Mints a public link to a report, valid for months unless a shorter expiration is set. Each call mints a new token and earlier links stay live until their own expiry, so repeated calls grow the set of public links rather than rotating one.
Segments
7- List Segments Lists the saved segments and the expressions behind them.
- Get Segment Reads one segment's definition.
- Create Segment Creates a segment from a query expression, which is how an agent hands a team a live slice of feedback to work from.
- Update Segment Updates a segment's expression or metadata.
- Delete Segment Deletes a segment. The feedback it selected is untouched.
- Attach Segment Link Creates a shareable link to a segment.
- Detach Segment Link Removes a segment's shareable link.
Organization
9- List Teams Lists the teams in the account.
- Get Team Reads one team, including its parent.
- Create Team Creates a team, typically mirroring a region, brand or business unit from an HR or identity system.
- Update Team Updates a team. Note that Feedier publishes no route for deleting one.
- List Users Lists the Feedier users, their roles and their teams.
- Get User Reads one user record.
- Create User Provisions a user with a role and a team. The joiner half of a directory sync.
- Update User Updates a user's role, team or details.
- Delete User Removes a user. The leaver half of a directory sync, and worth pairing with an ownership sweep so no record is left owned by nobody.
Workflows
4- List Workflows Lists the automation workflows configured in Feedier.
- Get Workflow Reads one workflow, including its nodes.
- Create Workflow Creates a workflow in Feedier for logic that belongs inside the platform rather than in a flow.
- Delete Workflow Deletes a workflow along with its nodes and its execution history. Feedier publishes no way to pause a workflow through the API, so deleting and recreating is the only way to switch one off, which makes this a heavier action than its name suggests.
Referentials
9- List Referentials Lists the reference tables that enrich incoming feedback, such as employees, stores or products.
- Get Referential Reads one reference table, including its column template. The read to run before any update, because updates replace the template.
- Create Referential Creates a reference table.
- Update Referential Updates a reference table. Sending the template attribute list replaces it outright, so any column left out is removed.
- Delete Referential Deletes a reference table and the enrichment that depended on it.
- List Referential Items Lists the rows in a reference table.
- Get Referential Item Reads a single row.
- Create Referential Item Creates a row. The attribute values sent replace the row's whole column set rather than merging into it.
- Delete Referential Item Deletes a row from a reference table.
Imports and Analytics
3- Upload CSV Import Starts an asynchronous import using a column mapping configured once in the Feedier dashboard. Returns the import as pending rather than the finished result.
- Get Import Reads an import's status and, once complete, its total, succeeded and failed row counts. The poll that lets a flow hold until an import actually lands, and the read that exposes a partially failed file.
- Evaluate KPI Formula Evaluates a KPI formula and returns the result, so a dashboard or a digest can quote Feedier's own calculation instead of rebuilding it. The result comes back as a string, so parse it before doing arithmetic.
Feedback Forms
3- List Feedback Forms Lists the feedback forms on the account.
- Get Feedback Form Reads one form's configuration.
- List Questions Lists a form's questions, which is how a flow maps answers to meaning when summarizing free text for a person.
Invitations
9- Send Email Invitation Sends a survey invitation by email, carrying custom fields that land on the resulting answer as attributes. The action behind an invitation triggered by a business event rather than a schedule.
- Send SMS Invitation Sends a survey invitation by SMS with the same custom field behavior. Each send reaches a real phone and cannot be recalled, so pair volume sends with a confirmed audience.
- List Sent Invitations Lists invitations already sent, with their delivery state. The read behind a chase or a deliverability check.
- List Push Campaigns Lists the push campaigns built in the Feedier dashboard. Campaigns cannot be created through the API, so this reads what already exists.
- Get Push Campaign Step Reads one step of a push campaign.
- Add Campaign Recipients Adds recipients to an existing campaign, which is how an audience assembled by a flow enters a campaign someone designed in the dashboard.
- List Push Unsubscribes Lists the suppression entries, so a flow can reconcile them against the opt outs recorded elsewhere in the stack.
- Create Push Unsubscribe Adds a target to the suppression list. The action to run the moment a CRM, help desk or email platform records an opt out, before the next campaign goes anywhere near that contact.
- Delete Push Unsubscribe Removes a suppression entry. Worth treating as a consent decision rather than a data cleanup, because it makes a contact reachable again.
Triggers
1 triggersEvent Triggers
1- On New Feedback Fires when new feedback arrives, optionally narrowed by a query language filter so a flow only wakes for the records it can act on. Feedier publishes no webhook API, so this trigger polls: the first cycle records a baseline and fires nothing, and each cycle inspects the most recent records rather than the full history. An account taking more new feedback between cycles than one page holds should narrow the filter or shorten the interval.
Frequently Asked Questions
What can FlowRunner do with Feedier?
FlowRunner agents can run List Feedback, Get Feedback, and Submit Feedback in Feedier, plus 58 more actions.
Does connecting Feedier to FlowRunner require OAuth?
No. Feedier connects to FlowRunner with an API key, no OAuth flow required.
Can Feedier trigger a FlowRunner workflow automatically?
Yes. Feedier supports 1 trigger that can start a FlowRunner workflow automatically.
Other Forms integrations
Start building with Feedier
Free plan, no card required. Connect in minutes.