Resources · Make integration

Ragic Make integrationAutomate Ragic with Make.

Can a new Ragic record start work in your other tools on its own? The Ragic Make integration gives you 5 modules: 2 instant triggers and 3 actions. This guide is for operations teams who run their data in Ragic forms, and it walks you from the connection to a first working scenario.

Try the Ragic integration on MakeSee the 5 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Ragic Make integration do for you?

The Ragic Make integration links your Ragic database to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that each do one job. Ragic can tell Make the moment a record is created or changed on a form, and Make can write records back into Ragic.

A handoff between two forms. A sales rep saves a new order in Ragic. Watch New Record picks it up, and Create a Record opens the matching entry on your fulfilment form, so nobody retypes it.

Status changes that travel. When someone edits a record, Watch Updated Record hands the new version to the rest of your scenario. Add a module of another app after it, and a status change in Ragic reaches your team chat or your CRM.

Records that fill themselves. Put Update a Record at the end of a scenario to write a result back into Ragic, for example a reference produced by another tool.

Know one limit before you start: Make marks its own documentation for Ragic as limited, because little public information about the app exists. When a listed module falls short, Make an API Call reaches the rest of the Ragic API with the same account. If you are still choosing a platform, read the n8n vs Make comparison, and the Make pricing guide explains how operations are counted. Teams that want a hand can ask the Make agency.

Connect

How do you connect your Ragic account to Make?

  1. 01

    Add a Ragic module

    Open your scenario, click the +, search for Ragic and pick any of its modules. Then click Create a connection: a connection is your Ragic account linked to Make once and reused by every Ragic module.

  2. 02

    Give it a clear name

    Naming the connection is optional, but it pays off the day you link a second Ragic account. A name like the database or the team it belongs to tells you at a glance which one a module uses.

  3. 03

    Authorize and save

    Follow what the window asks: either approve access on the Ragic page that opens, or paste the key Ragic gives you. Click Save, and Make can now list what it is able to read in your account.

First scenario

Your first scenario with Ragic

GoalWhen a new record is saved on one Ragic form, Make creates the matching record on another form.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big +. That first slot is where the module that starts everything goes.

  2. 02

    Pick Watch New Record

    Search for Ragic, choose Watch New Record and select your connection. It is an instant trigger: Ragic calls Make through a webhook when a record is created, so nothing waits on a timer.

  3. 03

    Choose the source form

    Point the trigger at the form your team fills in, such as incoming orders. Only records created on that form will start the scenario.

  4. 04

    Add Create a Record

    Click the + to the right of the trigger, add Ragic Create a Record and pick a different form as the target. Map each value from the incoming bundle, the record the trigger received.

  5. 05

    Test with Run once

    Click Run once, then save a test record in Ragic. Make shows the bundles each module received; check that the new record landed on the target form.

  6. 06

    Switch it on

    Once the test is clean, switch the scenario on. Each record it handles counts as operations on your plan, one per module run.

Triggers

What starts a Ragic scenario

2 modules start a scenario when something happens in Ragic. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Ragic as soon as it happens.

Ragic1Watch New Record

Watch New Record

Instant trigger

In Make“Triggers when creating a record on the specific form”

Starts your scenario each time someone creates a record on the Ragic form you pick, and hands that record to the next module as a bundle you can map field by field.

How it fires
instant, Ragic calls Make through a webhook as soon as the record is created.
When to use it
a form where new entries should trigger work elsewhere, like an intake form whose requests must reach a second form or another app.
Watch out
it only watches one form, so each form you want to watch needs its own Watch New Record.
Ragic2Watch Updated Record

Watch Updated Record

Instant trigger

In Make“Triggers when updating a record on the specific form”

Reacts to edits rather than new entries: when a record changes on the chosen form, your scenario receives the updated version and can pass the change along.

How it fires
instant, Ragic calls Make through a webhook as soon as the record is updated.
When to use it
a status or owner that someone edits by hand in Ragic and that other tools need to see.
Watch out
if the same scenario ends with Update a Record on this form, run it once and confirm the update does not start the scenario again.
Modules

What Make can do in Ragic

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

Ragic1

Create a Record

Action

In Make“Creates a record on Ragic”

Adds a new record to a Ragic form from data that arrived earlier in the scenario, so entries appear without anyone copying them.

When to use it
a lead from a web form, or an order from another Ragic form, that should become its own entry.
Watch out
it adds a record every time it runs, so a replayed test leaves duplicates to delete.
Ragic2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call”

Reaches any endpoint of the Ragic API through the connection you already set up, which covers what the four named modules leave out.

When to use it
you need something none of the listed modules offers, and Make's limited Ragic documentation gives no dedicated option.
Watch out
you write the request yourself, and Make's limited Ragic documentation does not describe the endpoints for you.
Ragic3

Update a Record

Action

In Make“Updates a record on Ragic”

Changes an existing Ragic record instead of adding one, so the entry your team already works in stays the single source of truth.

When to use it
writing a result back, such as a reference returned by an invoicing app or a status set by a later step.
Watch out
it needs to know which record to change, so map the identifier from the trigger or an earlier module.
Need help

Need help automating Ragic with Make?

A person reads every message.

FAQ

Questions about Ragic and Make

01Is the Ragic Make integration free?
Yes, Ragic is a standard app, so it is available from the Free plan. The Free plan keeps 2 active scenarios, runs scheduled scenarios at most every 15 minutes, stops each run after 5 minutes and caps transfer at 512 MB. Paid plans (Core, Pro, Teams and Enterprise) lift the interval to 1 minute and allow unlimited active scenarios. Usage is counted in operations: one module running on one bundle is one operation, so a scenario with a trigger and two actions uses three per record.
02What do you need to connect Ragic to Make?
A Ragic account that holds the forms you want to automate, and a Make account. Make's documentation for Ragic lists no prerequisites and is marked as limited. The connection follows Make's usual path: add a Ragic module, click Create a connection, name it if you like, then either authorize Make on the Ragic page or paste the key Ragic provides, and save. The same connection then serves all 5 Ragic modules, triggers and actions alike.
03Does the Ragic trigger in Make react in real time?
Yes. Both Ragic triggers, Watch New Record and Watch Updated Record, are instant: Ragic calls Make through a webhook as soon as a record is created or updated on the form you chose. You will see a lightning badge on them in the editor. The 15-minute default schedule of a new scenario applies to scheduled triggers, which Ragic does not have in Make, so switching the scenario on is enough for records to flow.
04What if a Ragic module you need is missing in Make?
Use Make an API Call. It sends any request to the Ragic API with the connection you already created, so you keep one account link for everything. Expect to write the request yourself: Make's documentation for Ragic is flagged as limited and does not describe the endpoints. If the need is simple, check first whether Create a Record or Update a Record already covers it. Each call counts as one operation, like any other module.
05Should you use Make or n8n for Ragic?
It depends on where the rest of your automations already run. In Make, Ragic comes with 5 modules, including 2 instant triggers and a Make an API Call module for anything else, and the Free plan is enough to try it. The same app often has an n8n node too, so check that side before you decide. Neither tool is ranked here: pick the one your team already builds in, and compare the Ragic modules each one offers.
Same platform

Other docs you might need on this stack.

Browse all integrations