Resources · Make integration

FaunaDB Make integrationAutomate FaunaDB with Make.

Can Make send data into your FaunaDB database without a line of backend code? Yes. The FaunaDB Make integration gives you 2 action modules, both built on GraphQL. This guide is for builders who already use FaunaDB and want to link the account, run a first query and switch a scenario on.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the FaunaDB Make integration do for you?

The FaunaDB Make integration lets a Make scenario (the automation you build, a chain of bricks called modules) talk to your FaunaDB database through GraphQL. It has no trigger of its own, so another app or a schedule starts the scenario, and FaunaDB receives the query.

Store what other tools collect. A new signup lands in your form tool, and Execute a GraphQL Query writes it into FaunaDB. The 123FormBuilder Make integration is one example of a source that can open that flow.

Read data back for the next step. The same module can fetch records, so a later module can reuse them in a message or a sheet. Each record that moves between modules is a bundle, one item passed along the chain.

Ship a schema change from a scenario. Import GraphQL Schema pushes a schema to your database, handy when a release process already runs in Make.

Make's own documentation flags this app as having limited documentation, so expect to rely on your FaunaDB knowledge for the query itself. If you are weighing tools for this job, the n8n vs Make comparison lays out the criteria, and the Make training covers scenario basics from zero.

Connect

How do you connect FaunaDB to Make?

  1. 01

    Add a FaunaDB module

    Open your scenario, click the +, search for FaunaDB and pick one of its two modules. Inside the module, click Create a connection. A connection is your FaunaDB account linked to Make once, then reused by both modules.

  2. 02

    Name it and authorize

    Give the connection a name if you like, for example the database it points to. Then authorize Make on the FaunaDB page that opens, or paste the key FaunaDB gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown. From here on, any FaunaDB module in any scenario can pick it without logging in again.

First scenario

Your first scenario with FaunaDB

GoalWhen another app sends a new record, Make runs a GraphQL query that saves it in FaunaDB.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. That first module comes from the app that holds your new data, since FaunaDB has no trigger.

  2. 02

    Connect the source app

    Search the source app by name, pick its module and click Create a connection. Fill its fields; Make lists what it can read once the connection exists.

  3. 03

    Add the FaunaDB module

    Click the + on the right of the first module, search FaunaDB and choose Execute a GraphQL Query. Pick your connection and write the query, mapping values from the previous module into it.

  4. 04

    Test with Run once

    Click Run once to run the scenario one time. Read the bundles each module received and confirm FaunaDB answered the way you expected.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario), then switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the FaunaDB modules do

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

FaunaDB1

Execute a GraphQL Query

Action

In Make“Performs an arbitrary authorized GraphQL query.”

This is your all-purpose door into FaunaDB: you write any GraphQL query your credentials allow, and the result comes back as data the next module can map. One module covers reading and writing, because the query decides what happens.

When to use it
a lead arrives from your form tool and needs a record in FaunaDB, or a report step needs rows pulled out first.
Watch out
test each new query with Run once before switching on, since Make has no documented guardrails for this app.
FaunaDB2

Import GraphQL Schema

Action

In Make“Imports GraphQL schema.”

Import GraphQL Schema sends a schema to your FaunaDB database, so the types and queries it defines become available without opening the FaunaDB console. It changes the structure, not the records.

When to use it
your team already versions the schema and wants the upload to follow a release event that another module announces.
Watch out
a schema import can affect every query that depends on it, so run it on a test database before production.
Need help

Need help automating FaunaDB with Make?

A person reads every message.

FAQ

FaunaDB and Make: common questions

01Is the FaunaDB Make integration free?
Yes, FaunaDB is a standard app, so it works from the Free plan onward. That plan gives you 2 active scenarios, a minimum of 15 minutes between scheduled runs, up to 5 minutes per execution, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes per run. Usage is counted in operations each month. FaunaDB's own pricing is a separate matter.
02What do you need to connect FaunaDB to Make?
A FaunaDB account with access to the database you want to reach, and a Make account. The documentation lists no other prerequisite. Add a FaunaDB module, click Create a connection, optionally name it, then authorize Make on the FaunaDB page or paste the key FaunaDB provides, and click Save. Make notes that its FaunaDB documentation is still limited, so if something fails, start by checking the credential on the FaunaDB side.
03Does the FaunaDB Make integration react in real time?
No, because FaunaDB has no trigger module in Make. A scenario that uses it starts some other way: from a trigger of another app, such as a form or a CRM, or from the schedule you set on the first module. A new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Paid plans can run as often as every minute. If you need an event to start things right away, pick a source app that offers an instant trigger.
04What if a FaunaDB module is missing in Make?
FaunaDB has only 2 modules in Make and no Make an API Call module, so you cannot fall back on a raw request from this app. The good news is that Execute a GraphQL Query accepts any query your credentials allow, which covers most reads and writes. If that still falls short, another app in the scenario can take over part of the job, or you can describe the use case in the contact block at the bottom of this page.
05Should you use Make or n8n for FaunaDB?
It depends on how you prefer to build. In Make, FaunaDB offers 2 GraphQL modules and no trigger, and Make's documentation for this app is limited. Before choosing, check whether the other tool covers the operations you need and how each one starts a workflow. The comparison page on this site lists the criteria side by side without ranking one tool above the other, which is a fair place to start.