Simplesat

Simplesat collects CSAT, NPS and CES feedback for service teams. Agents push feedback in, pull it back out, keep customers and team members in step with a helpdesk, send event based survey emails, and react to new feedback as it arrives.

Verified 2 triggers 19 actions API key available

Simplesat website Platform Documentation Capability data verified 2026-08-26

On New Response fires when a customer rates a closed ticket

Get Response returns the rating, the comment, the ticket reference and the team members credited

The credited technician is compared against who actually resolved the ticket in the service desk

Search Answers pulls the comment text so the manager reads the customer's own words

A mismatch posts to the service desk manager with both records side by side

The manager decides whether the response is re-attributed, corrected, or left exactly as the customer gave it

What This Integration Enables

Every other feedback tool in this category attaches a score to a product or an account. Simplesat attaches it to a person on your team. A response carries the survey, the customer, the ticket and the team members credited with the work, which is why service desks and managed service providers use it and why the data ends up in performance conversations. That changes what an agent is allowed to do with it.

FlowRunner agents keep the two systems in step, upserting customers and team members from the service desk on email address, sending event based survey emails when a ticket closes, and searching responses and answers by date range and field filter so a digest never walks whole records to find a comment. They also write: Create Or Update Response upserts on the ticket's external identifier so feedback gathered on a call lands in the same place as a web rating. What they hand back is any change to a rating or a comment a customer actually submitted, because on this connector that is somebody's review.

Without FlowRunner

Ratings arrive without their context A score lands in a dashboard with no ticket, no technician and no comment beside it

Customer records drift from the helpdesk Contacts are maintained in the service desk and in the survey tool, and the two disagree within a month

Corrections happen quietly A misattributed rating gets edited by whoever noticed, with no record of what the customer originally wrote

With FlowRunner

Every score carries its ticket Responses are read with the ticket, the customer and the credited team members attached, so a number is always explainable

One upsert keeps both in step Customers and team members are pushed from the service desk on a schedule, matched on email address

Corrections are decided, not applied Edits to a rating or a comment are proposed with the original shown, and a person authorizes the change

Use Case Scenarios

The survey goes out because the ticket closed, not because it is Thursday

A ticket resolves in HaloPSA or Zendesk. The agent calls Create Or Update Customer so the contact record matches what the service desk holds, resolves the survey token with List Surveys, and calls Send Survey Email against the event based survey. When the customer answers, On New Response fires, and the agent posts the rating with the ticket link and the comment into the team channel in Slack. The feedback loop closes in hours instead of at the end of a reporting period, and the technician sees the response while they still remember the ticket.
Customer and team member records that stay current on their own

On a schedule, the agent pulls contacts changed in the service desk and calls Bulk Upsert Customers in batches, then compares the records Simplesat returned against what it sent, because the bulk route ignores invalid rows silently and still answers success. Rows that did not land are reported rather than assumed. Team members get the same treatment through Create Or Update Team Member, matched on email address, so a new hire is surveyable on their first closed ticket rather than after someone remembers to add them.
A comment digest that does not walk the whole dataset

Search Answers is the fastest path to comment text, ratings and sentiment without pulling entire response records, so a weekly digest agent searches answers over the period, groups them by team member and by topic, and writes the summary to Google Sheets alongside the counts. Responses that carry a low rating and a long comment are pulled in full with Get Response and routed to the manager individually. The report reads like a review of the work rather than a chart of numbers.

Human-in-Loop Highlight

Update Answer changes the choice or the comment stored against a question, and Update Response changes the record that comment belongs to. On Simplesat, that record is a rating a named technician is measured on, and Delete Response removes it outright through a route the vendor does not even publish. So when an agent finds a response credited to the wrong person, or a rating that arrived against a ticket the team never touched, it does not fix it. It assembles the case and stops: "This response scores a technician who is not on the resolving ticket in the service desk, and the customer's comment names a different engineer. Re-attribute the response, leave it and annotate the ticket, or delete it?" The service desk manager answers. Reconciling two systems is exactly the work to hand an agent. Editing what a customer said about a named colleague is not, and neither is deciding whose score a bad rating belongs to.

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

19 actions

Responses

Search Responses Searches responses with independent created and modified date ranges plus any number of field filters. The entry point for digests, audits and reconciliation sweeps.
Get Response Retrieves the full record: survey, customer, ticket, team members, answers and topics. Used when a score has to be explained rather than counted.
Create Or Update Response Upserts a response on the ticket's external identifier, so feedback captured on a call or in another tool lands in the same place as a web rating. Requires a survey and at least one answer when creating.
Update Response Corrects or enriches an existing response. Changes a record a named team member is measured on, so it sits behind this page's human gate.
Delete Response Deletes a response. The route is undocumented by the vendor and shipped because the API's own verb listing advertises it unambiguously. There is no undo.

Answers

Search Answers Pulls comment text, ratings and sentiment directly, without walking whole responses. The fastest read on the connector and the one most digests should use.
Get Answer Retrieves a single answer with its question and its stored value.
Update Answer Changes the choice, choices or comment on an answer. This edits what the customer submitted, which is why it is gated.

Customers

List Customers Lists customers with created and modified date filters and a subscription filter.
Get Customer Retrieves one customer record.
Create Or Update Customer Upserts a customer on email address. The operation that keeps the survey tool in step with the service desk.
Update Customer Updates a customer addressed by identifier rather than by email. Note that tags and custom attributes replace what is stored rather than merging, so send the complete set you want to keep.
Bulk Upsert Customers Upserts customers in batches. Invalid rows are ignored silently while the call still succeeds, so compare the returned records against what was sent.

Team Members

Get Team Member Retrieves one team member. The API publishes no list route for team members, so records are addressed by identifier or created by email.
Create Or Update Team Member Upserts a team member on email address. How a new hire becomes surveyable without anyone opening the dashboard.
Update Team Member Updates a team member by identifier. Another route the vendor does not publish but the API's own verb listing confirms.

Surveys and Questions

List Surveys Lists surveys, returning both the numeric identifier used by response writes and the token used by email sends and survey filters. The two are not interchangeable.
Send Survey Email Sends an event based survey to a customer. Only surveys configured as event based are accepted, which is the vendor's own guard against a flow mailing a campaign survey by mistake.
List Questions Lists questions with the identifiers the response write operations expect on each answer.

Triggers

2 triggers

Event Triggers

On New Response Fires when new feedback arrives, optionally restricted to one survey. Simplesat's webhooks are configured in the product interface and have no management API, so this polls the response search endpoint instead. It establishes a baseline on the first poll and keeps a window of already reported identifiers alongside the timestamp, because the vendor's date filters have second precision and a record created in the same second as the previous poll would otherwise fire twice.
On New Customer Fires when a new customer record appears. Polls the customer listing on a created after filter, with the same baseline and deduplication behavior.

Frequently Asked Questions

What can FlowRunner do with Simplesat?

FlowRunner agents can run Search Responses, Get Response, and Create Or Update Response in Simplesat, plus 16 more actions.

Does connecting Simplesat to FlowRunner require OAuth?

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

Can Simplesat trigger a FlowRunner workflow automatically?

Yes. Simplesat supports 2 triggers that can start a FlowRunner workflow automatically.

Start building with Simplesat

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us