Resources · Make integration

Askara Make integrationAutomate Askara with Make.

Can new Askara documents and patient records flow into the rest of your stack without copy and paste? The Askara Make integration gives you 3 modules: one trigger and two actions. This guide shows what each one does, how to link your account and how to build a first scenario you can test.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Askara Make integration automate?

The Askara Make integration links your Askara account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger or an action. With it, a new document in Askara can start a chain of steps, and data from another app can become a patient record in Askara.

Patients created from an intake form. Put a form or CRM module from another app first, then add Create a patient. Each submission becomes a record in Askara, so nobody retypes names from an email.

A team heads-up on every new document. Start with Watch new document and send the details to a chat or email app. The person who handles documents learns about them without opening Askara.

Anything the listed modules skip. Make an API Call reaches any endpoint of the Askara API with the same connection, which covers actions the two ready-made modules leave out.

Be aware of one limit: Make itself says its Askara documentation is incomplete, because little public information exists about the app. Field details are not published, so plan to explore them in the editor. If you compare tools, the n8n vs Make page lays out the differences, the Make review covers the editor in depth, and Make training helps if you are starting out.

Connect

How do you connect Askara to Make?

  1. 01

    Add an Askara module

    In your scenario, click the + and search for Askara, then pick any of its modules. Click Create a connection. A connection is your Askara account linked to Make once, and every Askara module reuses it.

  2. 02

    Name it and authorize

    Give the connection a name if you like, for example the clinic or workspace it belongs to. Then either approve Make on the Askara page that opens, or paste the key Askara provides, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Make returns to the module and can now read what your Askara account exposes. From here on, pick this connection in any Askara module instead of creating a new one.

First scenario

Build your first scenario with Askara

GoalWhen a form in another app receives a new entry, Make creates the matching patient in Askara.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot holds the module that starts everything.

  2. 02

    Start with your form app

    Search for the form or booking app your team already uses, pick the module that watches new entries and click Create a connection to link that account.

  3. 03

    Add Create a patient

    Click the + on the right of the first module, search for Askara and choose Create a patient. Select your Askara connection, then click the values from the form to fill its fields.

  4. 04

    Test with Run once

    Send a test entry through the form, then click Run once. Each module shows the bundles it received, a bundle being one item passed along, here one entry.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then turn the scenario on. New patients now appear in Askara without you.

Triggers

What starts an Askara scenario?

1 module starts a scenario when something happens in Askara. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Askara as soon as it happens.

Askara1Watch new document

Watch new document

triggerIn the docs only

Your scenario picks up every document added to Askara since the last check and hands each one to the next module as its own bundle, so follow-up work starts without anyone watching the account.

How it fires
scheduled: Make checks the app on the scenario's schedule. The module type comes from its name, since Make's directory entry was unavailable, so confirm the clock badge in the editor.
When to use it
when a new file in Askara should trigger a notification, a copy or a record elsewhere.
Watch out
on the Free plan, two checks sit at least 15 minutes apart, so reactions are not immediate.
Modules

What else can Make do in Askara?

Askara gives you 2 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Askara1

Create a patient

ActionIn the docs only

You get a new patient record in Askara built from data that arrives in the scenario, such as a form answer or a contact from another tool, without typing it by hand.

When to use it
after an intake form or booking app, when each new person should exist in Askara too.
Watch out
Make does not document the fields of this module, so run it once with test data and check the result in Askara before you switch the scenario on.
Askara2

Make an API Call

ActionIn the docs only

This module opens the rest of the Askara API to your scenario, reusing the connection you already created, so you can reach an endpoint that no ready-made module covers.

When to use it
when you need something beyond watching documents or creating patients, and Askara's own API reference describes the call.
Watch out
you write the request yourself, so read Askara's API documentation first; Make's page for this app is incomplete.
Need help

Need help automating Askara with Make?

A person reads every message.

FAQ

Askara and Make: common questions

01Is the Askara Make integration free?
Yes, Askara is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Each module run on one bundle counts as one operation, and Make meters those as credits each month.
02What do you need to connect Askara to Make?
An Askara account and a Make account. Add any Askara module, click Create a connection, optionally name it, then either authorize Make on the Askara page or paste the key Askara gives you, and click Save. Make lists no specific prerequisite for Askara, because its documentation for this app is limited. If the authorization step asks for something unexpected, Askara support is the right place to ask which credentials it expects.
03Does the Askara trigger in Make work in real time?
No. Watch new document behaves as a scheduled trigger, a type inferred from its name because the directory entry was unavailable. Make checks Askara on the scenario's schedule, every 15 minutes by default, with 15 minutes as the minimum on the Free plan and 1 minute on paid plans. Anything added between two checks is picked up on the next one, each document arriving as a separate bundle for the following modules. If you need Askara documents to reach another tool faster than that, the schedule of the scenario is the setting to adjust.
04What if the Askara module you need is missing in Make?
It depends on the Askara API. The ready-made modules only watch new documents and create patients, but Make an API Call reaches any endpoint of the Askara API with the same connection. You build the request yourself from Askara's API reference. Keep in mind that Make says its own documentation for Askara is incomplete, so testing each call with Run once before activation saves surprises later. The Make troubleshooting resources help when a call returns an error you do not understand.
05Should you use Make or n8n with Askara?
It depends on the tool you already use. Make offers Askara 3 modules: one trigger and two actions, including a generic API call. Many apps also have an n8n node, so check whether one exists for Askara before choosing. Base the decision on the modules each tool actually offers for your case and on the editor your team is comfortable with, then test the flow in the tool you pick.