Askara
ERPConnect AI agents to Askara, the medical practice platform for French healthcare providers. Agents read and write patient records, manage professional contacts and organizations, and retrieve clinical documents and notes.
What This Integration Enables
This connector handles patient health-record data, and that fact should shape how it is used before anything else about it is interesting. The extension's own documentation is explicit: route its output only to destinations approved for patient information. FlowRunner does not change what a practice is permitted to do with a patient record, and neither Askara nor FlowRunner is described here as certifying any regulatory scheme. What this page describes is what the connector can read and write, and where a person should stand in the middle of it.
Askara is a medical practice platform for French healthcare providers. Agents read and write patient records, read and write the professional contacts a practice refers to such as doctors, specialists and laboratories, retrieve the documents Askara generates including consultation reports and referral letters, retrieve the clinical notes produced from recorded consultations, and work with the consultation audio recordings themselves. A separate speech-to-text host, reached with its own key, transcribes an audio file to text. Five webhook triggers report new patients, new contacts, new documents, new notes, and a change in a document's third-party synchronisation status, which is reported back by the flow itself through Set Document Synchronization Status. That last pairing is the part worth designing around: a practice can see, inside Askara, whether the letter it generated actually landed in the system it was meant for, and read the error text when it did not.
Two constraints deserve stating plainly rather than in a footnote. Create Or Update Patient matches on the French social security number, or failing that on the combination of first name, last name and date of birth, and it deliberately never matches on an external ID because source-software folder numbers can be reassigned. And Transcribe Audio requires an audio URL that Askara can download without authentication, which is a decision about consultation recordings that a practice makes deliberately, not one an automation should make on its behalf.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Intake that reaches the practice record without being retyped
A prospective patient completes an intake form. The agent reads the identity fields, searches List Patients on name and date of birth, and inspects what comes back. Where the form carried a social security number and exactly one record matches, or where no record exists at all and the identity is complete, the agent calls Create Or Update Patient and the intake is done. Where the identity is partial, or two records share a name and a birth date, the agent writes nothing and asks a practice user. The administrative work is automated. The identification is not.
Generated correspondence routed to the system that needs it
Askara generates a referral letter and On New Document fires. The agent retrieves the document with Get Document, confirms the linked patient, and pushes it into the practice's approved document store or correspondence system. It then calls Set Document Synchronization Status to record the outcome in Askara, sending a short error message where the push failed. On Document Synchronized fires on that status change, so a retry flow can pick up failures without anyone watching a queue. The practice sees the state of every generated document in the platform it already works in.
Referral network kept current from the practice's own directory
A referring specialist changes address or a new laboratory is added to the practice's directory. The agent resolves the record with List Contacts, then calls Create Contact or Update Contact, marking the contact as a doctor and setting the specialty so Askara addresses generated correspondence correctly. Contact records hold professional details rather than patient information, so this is the part of the connector that runs with the least ceremony, and keeping it accurate is what stops a correctly generated letter going to a stale address.
Human-in-Loop Highlight
The gate on this connector is any write that reaches a patient record, and the reason is specific rather than general. Create Or Update Patient matches on the French social security number when it is present, and on first name, last name and date of birth when it is not. That second rule is a reasonable identity heuristic and it is not a guarantee. Two people can share a common surname, a common first name and a date of birth, and an intake form filled in on a phone can arrive with the social security number missing or mistyped. When that happens, the write does not fail. It succeeds, against the wrong person's record, and the practice inherits a chart with two people's information in it. That is not a data quality problem to be cleaned up in a quarterly audit. It is a patient safety problem, and it is the kind of error that is easiest to prevent at the moment of the write and hardest to unpick afterwards.
So FlowRunner puts a person at exactly that point. The agent does the work that does not need judgment: it reads the form, normalises the fields, searches the existing records, and assembles the comparison. Then it checks two conditions. Where the social security number is absent, or the name and date of birth match more than one record, the write becomes a human-in-the-loop step. The agent stops and asks a named practice user through the channel the practice has chosen: "Intake form for Martin Lefevre, born 14/03/1978, no social security number supplied. Two existing patients match that name and date of birth. Create a new record, update record A, update record B, or leave this to me?" Nothing is written until that answer arrives, and the answer and the person who gave it are recorded alongside the change.
The same principle governs the rest of the connector. An agent can move a generated document to an approved destination, report whether that move succeeded, transcribe a recording the practice has decided to make available, and keep the referral directory accurate. It does not interpret clinical content, and it does not decide anything about a patient's care. Clinicians make clinical decisions. The agent handles the administration around them and stops the line when identity is in doubt.
Agent Capabilities
21 actionsPatients
4- List Patients Retrieves a page of patient records from the connected practice, with optional free-text search and filtering by name, email or phone, paginated up to 100 records per page and sortable by any indexed field. This reads patient health-record data, so route the output only to destinations approved for patient information.
- Get Patient Retrieves a single patient record by its Askara UUID, including demographics, contact details and record identifiers. Use List Patients to find the UUID. This reads patient health-record data.
- Create Or Update Patient Creates a patient record, or updates the existing one when a match is found. Askara matches on the French social security number, or on the combination of first name, last name and date of birth. The external ID is stored but never used for matching, because source-software folder numbers can be reassigned. This writes patient health-record data and is the action that belongs behind an approval whenever the identity is not unambiguous.
- Update Patient Applies a partial update to an existing patient record identified by UUID. Only the fields supplied are changed and everything left empty is preserved. Unlike Create Or Update Patient this never creates a new record, which makes it the safer choice when the UUID is already known. This writes patient health-record data.
Contacts
4- List Contacts Retrieves a page of professional contacts held by the practice, covering referring doctors, laboratories and specialists, with optional free-text search and filtering by name, specialty, email or city. Paginated up to 100 records per page.
- Get Contact Retrieves a single professional contact by its Askara UUID, including specialty, practice details and postal address.
- Create Contact Creates a professional contact such as a referring doctor, specialist or dental laboratory. Marking the contact as a doctor and setting a specialty lets Askara address generated correspondence correctly.
- Update Contact Applies a partial update to an existing professional contact identified by UUID. Only the fields supplied are changed and everything left empty is preserved.
Documents
3- List Documents Retrieves a page of documents Askara generated for the practice, such as consultation reports and referral letters, filterable by patient, document type or synchronisation state, with an expand option to inline the related patient, user or PDF objects. Documents contain patient clinical content.
- Get Document Retrieves a single generated document by its UUID, including its type, linked patient and generation metadata. Documents contain patient clinical content.
- Set Document Synchronization Status Reports back to Askara whether the flow successfully pushed a document into a third-party system, with an optional error message up to 2000 characters where it did not. Askara uses this to drive its document synchronisation event, so a failure becomes visible inside the practice platform rather than only in a log.
Notes
2- List Notes Retrieves a page of clinical notes captured by Askara, optionally scoped to one patient, one audio recording or a single note type. Notes hold the structured output of a recorded consultation and contain patient clinical content.
- Get Note Retrieves a single clinical note by its Askara UUID, including its type and the patient and audio recording it was derived from. Notes contain patient clinical content.
Audio
2- List Audio Recordings Retrieves a page of consultation audio recordings held by the practice, with optional free-text search and filtering by patient, recording user, spoken language or archive state, and an expand option to inline the linked patient. These recordings capture patient consultations.
- Get Audio Recording Retrieves a single consultation audio recording by its Askara UUID, including the linked patient, spoken language and archive timestamp. These recordings capture patient consultations.
Speech To Text
1- Transcribe Audio Submits an audio file to the Askara speech-to-text service and returns its text transcription, with the finished transcription also posted to a callback URL. The audio URL must be downloadable without authentication, which is a decision about consultation recordings for the practice to make deliberately. This endpoint lives on a separate speech-to-text host and uses its own key rather than the main API token.
Practice and Users
4- List Organizations Retrieves the practices the connected account belongs to, including postal address, timezone, registration identifiers and the dental nomenclature system in use, with an expand option to inline the practice users or registered webhooks.
- Get Organization Retrieves a single practice by its Askara UUID, including address, contact details, timezone, preferred currency and nomenclature settings.
- Get Current User Retrieves the Askara user account the API token belongs to. Use it to confirm a connection works and to discover the user UUID and the practice the token is scoped to before running anything else.
- Get User Retrieves an Askara practice user by UUID, for example the practitioner recorded as the author of a document or an audio recording.
Webhooks
1- List Webhooks Retrieves the webhook subscriptions registered on the practice, including callback URL, enabled state and subscribed events. Useful for auditing which endpoints Askara is currently notifying, including those created by this extension's triggers.
Triggers
5 triggersEvent Triggers
5- On New Patient Fires when a new patient record is created in the connected practice. Used to start an onboarding or record-sync workflow at the moment the patient exists. The extension registers a webhook on Askara's new patient event and passes the delivered payload through, so the flow receives patient identity data.
- On New Contact Fires when a new professional contact is created in the practice. Used to mirror a new referring doctor, specialist or laboratory into a directory the practice maintains elsewhere.
- On New Document Fires when Askara generates a new document such as a consultation report or referral letter. Used to route the document to an approved destination and report the result back. The payload references a document containing patient clinical content.
- On New Note Fires when Askara produces a new clinical note from a recorded consultation. Used to move the note into an approved store or review workflow. The payload references a note containing patient clinical content.
- On Document Synchronized Fires when a document's third-party synchronisation status changes, as reported through Set Document Synchronization Status. Used to drive a retry on failures, or to close the loop on a successful push without polling for it.
Frequently Asked Questions
What can FlowRunner do with Askara?
FlowRunner agents can run List Patients, Get Patient, and Create Or Update Patient in Askara, plus 18 more actions.
Does connecting Askara to FlowRunner require OAuth?
No. Askara connects to FlowRunner with an API key, no OAuth flow required.
Can Askara trigger a FlowRunner workflow automatically?
Yes. Askara supports 5 triggers that can start a FlowRunner workflow automatically.
Start building with Askara
$100 in credits. No card required. Connect in minutes.