Flixcheck

Flixcheck is a German platform for digital customer interaction: a check is a personalized form sent by SMS, email or WhatsApp and returned as structured data, files and signatures. Agents create and send checks, read the answers and documents that come back, download the PDF, and manage templates, teams and users.

1 trigger 67 actions API key available

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

A new claim, application or onboarding case is opened in the core system

Agent reads the customer's contact details, the case type and the case reference

Create Check sends the matching template to that one recipient by SMS, email or WhatsApp

On Check Event confirms the answer arrived, and Get Check reads the structured responses

List Check Element Files and Download File pull the photographs, scans and signed PDF

Update Check Custom Values writes the case number back onto the check record

The case handler reviews the evidence and the declared amount before the case moves forward

What This Integration Enables

A Flixcheck check is not a form you publish and hope somebody fills in. It is addressed to one named person, delivered to their phone, and it comes back as structured data, uploaded files and a legally usable signature. That is why insurers, banks, energy suppliers and telecoms use it for damage reports, onboarding and consent rather than a generic form builder. It is a customer interaction with an audit trail, and the platform is German, which matters when the answers and the signatures have to stay in the EU.

FlowRunner agents work the whole shape of that interaction. They send the check when the case opens, read the answers back the moment they arrive, pull the customer's photographs and signed documents into the case file, and write the case number onto the check so every later event carries it. They also chase: unanswered checks get a reminder, undeliverable ones get escalated to a person rather than sitting in a queue. What the agent never does is decide that the evidence is good enough. That judgment is a human-in-the-loop step by default, because the customer is a real person and the document is going into a file that may be read by a regulator.

Without FlowRunner

Document collection runs on post and email A customer is asked for photographs and a signature, then chased across channels for a week

Answers arrive as attachments Photographs and PDFs land in an inbox and are filed by hand into the case record

Nobody can see where a request is stuck Whether a customer has opened the form at all is invisible until they reply

With FlowRunner

The request goes out when the case opens The check leaves the moment the case is created, addressed to the named customer on their own phone

Answers arrive as structured data and filed documents Responses map onto case fields and the uploaded files land in the document library automatically

Silence is a signal the flow acts on Unanswered and undeliverable checks are chased or escalated rather than waited on

Use Case Scenarios

A claim opens and the customer is already answering

A new claim reaches the agent from the core system. It calls Create Check with the damage report template, addressed personally to the policyholder, delivered by SMS. When On Check Event reports the check answered, Get Check returns the structured answers, List Check Element Files and Download File retrieve the photographs and the signed declaration, and SharePoint receives them into the claim's document library. The confirmed address and consent flags go back onto the customer record in HubSpot, and Update Check Custom Values stamps the claim number onto the check so every later webhook carries it.
Silence and bounces stop being invisible

On a schedule, the agent calls List Checks for forms still unanswered after a week and runs Resend Check Link on each, logging the chase to Google Sheets. Send Message To Check Recipient adds a short note where a reminder alone is not enough. When On Check Event reports an email or SMS as undeliverable, that is not a retry case, it is a bad contact record: the agent posts the check identifier and the reason to the case team in Slack so someone can find a working number before the deadline passes.
The annual data review that goes out to everyone at once

A yearly obligation requires every customer in a segment to confirm their details. The agent reads the list, calls Create Check Batch against the template, and adds recipients with Add Check Batch Recipients in pages. It then calls List Check Batch Tasks and presents the assembled draft: how many recipients, which channel each will use, and which rows have contact data that will not deliver. Nothing is sent yet. Only after the operations owner confirms does the agent call Start Check Batch, and Get Check Batch tracks delivery from there.

Human-in-Loop Highlight

Start Check Batch is the one call on this connector with no way back. While a batch is a draft, recipients can be added and withdrawn freely. The moment the batch starts, Flixcheck begins delivering to every recipient in it, and there is no action here or anywhere else that recalls an SMS a customer has already received. Flixcheck built the draft state precisely because that boundary is real, so the agent works inside it and stops at the edge: "The 2026 data review batch is assembled as a draft. 1,412 recipients, 1,180 by SMS and 232 by email, using template Datenabgleich. 37 rows have no reachable contact and will fail. Start the batch, or hold while those are fixed?" The operations owner answers in Slack. Building the batch, deduplicating it and catching the unreachable rows is machine work. Deciding that fourteen hundred customers should hear from the company today is not.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via Slack

Human decides

Agent resumes with decision

Agent Capabilities

67 actions

Checks

Create Check Creates and sends a personalized check to one recipient, from scratch or from a template, by SMS, email or WhatsApp. A neutral check needs only a recipient name; a personal one takes gender plus first and last name.
Get Check Reads one check, including the recipient's answers once they have submitted. The follow up read after a trigger event, which carries identifiers rather than content.
Download Check PDF Renders a check as a PDF. In this API the PDF is the same route as the check chosen by content type, which is why this action takes layout flags rather than the usual read options. Left blank, those flags follow the team's own export settings.
List Checks Lists checks with filtering and ordering. Paged with a resume string rather than a page number, so a flow feeds the previous result's value back in.
Get Unread Check Count Returns how many checks are unread, which is the cheapest way for a flow to decide whether an inbox needs attention at all.
Move Check To Folder Files a check into a folder. Flixcheck's patch route accepts exactly one field per call, which is why this and the six actions below are separate rather than one update.
Set Check Open State Opens or closes a check, for example closing one whose deadline has passed.
Set Check Read State Marks a check read or unread, so an agent that has processed a response does not leave it looking untouched.
Hand Over Check To User Transfers a check to a colleague. The assignment step when triage decides who owns the case.
Update Check Notes Writes internal notes onto the check record, where the next person to open it will see them.
Rate Check Applies a rating to a check, which is how an automated assessment or a quality review is recorded on the record itself.
Update Check Custom Values Writes custom values such as a case or claim number onto the check, so the inbox and every later webhook event carry your own identifier.
Resend Check Link Sends the recipient their link again. The chase action for a check that has gone unanswered.
Send Message To Check Recipient Sends the recipient a message on the existing check, for when a reminder needs a sentence of context.
Cancel Scheduled Check Task Cancels a scheduled task on a check before it runs, for example a queued reminder that a manual phone call has made unnecessary.
List Check Element Files Lists the files a recipient attached to a check's elements. The read that finds the photographs and scans before downloading them.
Search Searches across checks, which is how a flow resolves a customer or case reference to the check that carries it.

Templates

List Templates Lists templates. With no folder specified it returns only unfiled templates, so ask for every folder when auditing the full set.
Get Template Reads one template, including its elements. Request a field list when only identifiers are needed, because a full template is large.
Create Template Creates a template, which is how a form defined in another system becomes a sendable check.
Update Template Updates a template. A full replacement on the wire, so this action reads the current record and lays your changes over it; sending elements still replaces the element set outright.
Copy Template Duplicates a template, the safe way to version a form that is already in use.
Delete Template Moves a template to the trash.
Empty Template Trash Permanently removes every template in the trash, with no undo. Worth running only on a reviewed list.

Folders

List Check Folders Lists the folders that organize checks.
List Folders Lists folders, including those used for templates.
Get Folder Reads one folder's configuration.
Create Folder Creates a folder, for example one per case type or per branch.
Update Folder Updates a folder. A full replacement on the wire, so this action merges your changes over the current record.
Delete Folder Removes a folder and everything filed in it. Standard folders such as the inbox cannot be deleted.

Files

Upload File Uploads a file and returns an identifier a check or template element can reference. A freshly uploaded file that is never referenced expires on its own, and one identifier can be reused across many checks.
Get File Reads a file's metadata.
Download File Downloads a file's content into FlowRunner file storage. The step that moves a customer's photograph or signed PDF into the document management system.
Rotate File Rotates an image, which is a small mercy when a customer photographs a document sideways.
Delete File Deletes a file. Flixcheck also removes a file once the last check referencing it is gone, so treat deletion as final.

Batch Sending

Create Check Batch Creates a batch from a template as a draft. Nothing is delivered at this point.
Get Check Batch Reads a batch's status and progress, before or after it starts.
Add Check Batch Recipients Adds recipients to a draft batch, in pages for a large audience.
List Check Batch Tasks Lists the individual sends in a batch. The read that lets a person see exactly who is about to be contacted, and how.
Delete Check Batch Task Withdraws one recipient from a batch. Only possible while the batch is still a draft.
Start Check Batch Releases the batch for delivery to every recipient in it. The point of no return, and the operation this page's human gate exists for.

Users and Teams

List Users Lists the account's users.
Get User Reads one user record.
Create User Creates a user, the joiner half of a directory sync.
Update User Updates a user. Flixcheck marks every field on its user route required, so this action reads the record first and lays your changes over it rather than blanking what you leave empty.
Delete User Removes a user. Reassign their open checks with Hand Over Check To User first.
Set User Signature File Attaches a signature file to a user, used where outgoing documents carry a named signature.
Create Login Token Produces a credential that signs a user straight into the portal. Hand it out through a redirect rather than storing it anywhere.
Get Team Reads a team's configuration, including the export settings that cascade to its members.
Get Team Structure Reads the team hierarchy, which is how a flow resolves who sits above whom before assigning or impersonating.
List Team Users Lists the members of a team.
Update Team Updates a team's settings.

Managed Lists

List Managed Lists Lists the option lists that feed dropdowns inside checks, such as branch offices, product codes or damage categories.
Get Managed List Reads one list and its entries. The read to run before any update.
Create Managed List Creates an option list.
Update Managed List Updates a list. The entry set is replaced outright, so entries not included are removed. Drive it from a full export rather than a delta.
Delete Managed List Deletes an option list and the choices it offered.

Document Types

List Custom Document Types Lists the custom document types used for information extraction from uploaded documents.
Get Custom Document Type Reads one document type, including the information it is set to extract.
Create Custom Document Type Defines a new document type, which is how a specific extraction contract enters the platform.
Update Custom Document Type Updates a document type. Sending the desired information list replaces it outright.

Widgets

List Widgets Lists the widgets configured on the account.
Create Widget Creates a widget, for example an entry point embedded in a customer portal.

Webhooks

List Webhooks Lists the registered webhooks and their state. Worth checking when a trigger has gone quiet, because Flixcheck pauses a webhook that keeps failing and reactivation is a manual step in the portal.
List Webhook Transactions Lists deliveries, including failed and queued ones. The read that distinguishes a broken flow from a paused subscription.
Run Webhook Transaction Replays a single delivery, so a queued or failed event can be processed without asking the customer to do anything again.

Reporting

List Activities Lists account activity, which is the audit read behind a compliance report or a usage review.

Triggers

1 triggers

Event Triggers

On Check Event Registers a real Flixcheck webhook on the account and removes it when the flow stops. It fires on notification events, such as a check being answered, opened, or reported undeliverable, and carries the account, user and check identifiers plus the properties belonging to that event rather than the recipient's answers, so follow it with Get Check when the content is needed. Flixcheck applies no signature to its deliveries, so setting the connection's webhook secret is recommended: the trigger then registers a header on the webhook and refuses any delivery that does not present it. Flixcheck's synchronous validation events are deliberately not offered here, because they hold the customer on the answer page waiting for an allow or refuse decision, and an asynchronous flow cannot honestly serve that contract.

Frequently Asked Questions

What can FlowRunner do with Flixcheck?

FlowRunner agents can run Create Check, Get Check, and Download Check PDF in Flixcheck, plus 64 more actions.

Does connecting Flixcheck to FlowRunner require OAuth?

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

Can Flixcheck trigger a FlowRunner workflow automatically?

Yes. Flixcheck supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Flixcheck

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us