Resources · Make integration

FoundationX Make integrationAutomate FoundationX with Make.

Can Make drive your FoundationX workflows and conversations for you? The FoundationX Make integration offers 18 modules: 14 actions and 4 searches, with no trigger. This page explains each one simply and walks you through a first scenario, from connection to switch-on.

Try the FoundationX integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the FoundationX Make integration do?

The FoundationX Make integration lets a Make scenario, the automation you build in Make, work inside your FoundationX account without code. Each module, one brick of that scenario, does one job: start a workflow, send a message to a conversation, save a source to your organisation or list your projects.

Launch a workflow from another tool. Since FoundationX has no trigger, the scenario starts on another app's event or on a schedule, then calls Run Workflow. List Workflow Runs and Get Results follow up on what happened, judging by their names.

Feed your organisation with new material. A file that lands elsewhere can go through Save File to Organisation, then Link Source to Project attaches the source to the right project. List All Sources shows what is already stored.

Keep conversations tidy. Create Conversation opens a thread, Create Message No Stream adds a message to it, and Get All Conversations or Delete Conversation help you review and clean up.

One honest limit: Make's own documentation says it cannot fully document FoundationX because too little public information exists. The fields each module shows once the connection exists are your best guide, and the Make troubleshooting page helps when a run fails. FoundationX may also have an n8n node; the n8n vs Make comparison lays out the differences. To get started on the editor itself, see the Make training.

Connect

How do you connect FoundationX to Make?

  1. 01

    Add a FoundationX module

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

  2. 02

    Name the connection

    This step is optional but useful. A clear name, such as the workspace it points to, helps you tell connections apart when a teammate adds a second FoundationX account to the same Make organization.

  3. 03

    Authorize Make and save

    Either approve Make on the FoundationX page that opens, or paste the key FoundationX gives you, depending on what the window asks. Then click Save. The module can now read your FoundationX data.

First scenario

Your first scenario with FoundationX

GoalWhen something happens in another app, Make starts a FoundationX workflow with Run Workflow, then reads its output with Get Results.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Here it comes from another app, since FoundationX offers no trigger of its own.

  2. 02

    Pick the starting event

    Choose the other app's module that should kick things off, and link its account through Create a connection. Each item it sends is a bundle, one piece of data flowing to the next module.

  3. 03

    Add Run Workflow

    Click the + on the right, search for FoundationX and pick Run Workflow. Connect your account, then fill the fields Make shows, mapping data from the first module where it fits.

  4. 04

    Add Get Results

    Click the + again and add Get Results, mapping what Run Workflow returned. That way the scenario reads back what the workflow produced and can pass it to another tool.

  5. 05

    Test with Run once

    Click Run once to execute the scenario one time. Open each module's bubble to read the bundles it received and check that the workflow started as expected.

  6. 06

    Schedule and switch on

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

Modules

What can the FoundationX modules do?

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

FoundationX1

Create Conversation

ActionIn the docs only

Opens a new conversation in FoundationX from your scenario, so every new request coming from another tool gets its own thread instead of piling into an old one.

When to use it
a support form or an intake email arrives and you want a fresh FoundationX thread for it.
Watch out
keep the conversation's ID from the output, since the message modules will need it later.
FoundationX2

Create Message No Stream

ActionIn the docs only

Posts a message into a FoundationX conversation and, as the name says, without streaming, so the module hands over one complete reply rather than a flow of fragments.

When to use it
you want to send a question to a conversation and pass the finished answer to the next module.
Watch out
the documentation gives no detail on its fields, so check what Make displays after connecting.
FoundationX3

Create Workflow Preview

ActionIn the docs only

Produces a preview of a FoundationX workflow, which, going by the name, lets you see what a workflow would give before committing to a real run.

When to use it
you are building the scenario and want to check a workflow's behavior before wiring Run Workflow.
Watch out
the documentation says nothing about what the preview contains, so test it with Run once first.
FoundationX4

Delete Conversation

ActionIn the docs only

Removes a FoundationX conversation for good, which keeps your account clean once a thread has served its purpose and its content is saved elsewhere.

When to use it
a ticket is closed in your helpdesk and its FoundationX thread no longer needs to exist.
Watch out
a deletion cannot be taken back, so place a filter before this module and test on a throwaway conversation.
FoundationX5

Get All Conversations

ActionIn the docs only

Fetches the conversations of your FoundationX account, giving you the full picture so that a later module can sort, archive or report on them.

When to use it
you want to copy every thread into a spreadsheet or check which ones are still open.
Watch out
it can return many bundles, and each one run through the next modules costs operations.
FoundationX6

Get Conversation by ID

ActionIn the docs only

Reads one specific conversation when you already hold its ID, which is far lighter than pulling every thread just to find a single one.

When to use it
an earlier module, or a record in your CRM, stored the ID and you need the thread's current state.
Watch out
map the ID from a previous module instead of typing it, or the scenario will always read the same thread.
FoundationX7

Get Message by ID

ActionIn the docs only

Retrieves one precise message from FoundationX by its ID, handy when you only need a single answer rather than the whole conversation around it.

When to use it
you logged a message ID earlier and now want its content to send by email or post in a chat tool.
Watch out
the module needs a valid message ID; map it from the module that created the message.
FoundationX8

Get Results

ActionIn the docs only

Brings back results from FoundationX, which, judging by its name, is how the scenario collects what a workflow produced and hands it on to your other tools.

When to use it
right after Run Workflow, to send the output to a document, a sheet or a teammate.
Watch out
the documentation does not say when results are ready, so check with Run once what the module returns.
FoundationX9

Get Text from Source

ActionIn the docs only

Pulls the text out of a source stored in FoundationX, so other apps can work with plain text instead of the original file or page.

When to use it
you saved a document as a source and want its text in a note, a database record or an email.
Watch out
long texts may be heavy for the next app; check what that app accepts before mapping everything.
FoundationX11

List All Sources

SearchIn the docs only

Searches the sources stored in your FoundationX organisation and returns each one as a separate bundle that the next modules can process.

When to use it
before adding a new source, to check whether the same material is already there.
Watch out
like any search, it can return zero, one or many items, so plan for the empty case with a filter.
FoundationX12

List Organisation Projects

SearchIn the docs only

Returns the projects of your FoundationX organisation, one bundle per project, which gives you the project IDs other modules ask for.

When to use it
you need to pick the right project for Link Source to Project or to sync the project list into a sheet.
Watch out
each project becomes a bundle, so every module placed after it runs once per project.
FoundationX13

List Workflow Runs

SearchIn the docs only

Shows the runs of your FoundationX workflows, so you can follow what has already executed without opening FoundationX itself.

When to use it
you want a log of runs in a spreadsheet, or to alert a teammate when a run needs a look.
Watch out
this search may return several runs; add a filter so you only act on the ones that matter.
FoundationX14

List Workflows

SearchIn the docs only

Lists the workflows available in your FoundationX account, which is the quickest way to find the one Run Workflow should start.

When to use it
you are setting up the scenario and want to know the exact workflows you can call.
Watch out
one bundle per workflow comes out, so the next modules run once per workflow unless you filter.
FoundationX15

Make an API Call

ActionIn the docs only

Calls any endpoint of the FoundationX API with the connection you already set up, which covers whatever the other listed modules leave out.

When to use it
you need a FoundationX feature that no listed module handles.
Watch out
you need to know the API yourself, since Make's documentation for FoundationX is limited and gives no endpoint list.
FoundationX16

Run Workflow

ActionIn the docs only

Starts one of your FoundationX workflows from Make, so an event in another tool can set your FoundationX automation in motion without a click.

When to use it
a new lead, a new file or a form answer should launch the matching workflow.
Watch out
test with Run once before switching on, because every run of the scenario will start the workflow again.
FoundationX17

Save File to Organisation

ActionIn the docs only

Stores a file in your FoundationX organisation, so documents arriving in your inbox or cloud drive become available to FoundationX without any upload by hand.

When to use it
an email attachment or a file added to a shared folder should reach FoundationX.
Watch out
on the Free plan, Make handles files up to 5 MB, so larger documents need a paid plan.
FoundationX18

Save Source to Organisation

ActionIn the docs only

Adds a new source to your FoundationX organisation. Judging by the name, it is the counterpart of Save File to Organisation for material that is not a file.

When to use it
new reference material appears in another tool and should become a FoundationX source.
Watch out
check List All Sources first if you want to avoid adding the same source twice.
Need help

Need help automating FoundationX with Make?

A person reads every message.

FAQ

Frequently asked questions

01Is the FoundationX Make integration free?
Yes, FoundationX is a standard app, available from Make's Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in credits, or operations, each month.
02What do you need to connect FoundationX to Make?
A FoundationX account and a Make account. Make's documentation lists no prerequisites and no official steps for this app, so the generic path applies: add a FoundationX module, click Create a connection, optionally name it, authorize Make on the FoundationX page or paste the key FoundationX gives you, then click Save. The same connection then serves every FoundationX module in your scenarios. Once saved, you do not have to connect again when you add another FoundationX module, in this scenario or in a new one.
03Does the FoundationX integration react in real time?
No, FoundationX has no trigger in Make, so nothing fires on its own when something changes in FoundationX. You start the scenario another way: with a trigger from another app, such as a new form answer, or with the schedule on the first module, every 15 minutes by default. The Free plan keeps at least 15 minutes between scheduled runs; paid plans go down to 1 minute. To react as soon as something happens elsewhere, pick an instant trigger in the other app, the module with the lightning badge.
04What if a FoundationX module is missing in Make?
Use Make an API Call. It reaches any endpoint of the FoundationX API with the connection you already created, so it covers what the 18 listed modules leave out. The catch is that Make's documentation for FoundationX is limited, because too little public information exists, so you will need the FoundationX API reference on your side to know which endpoint to call. Since the call reuses your existing connection, there is no second authentication to set up before using it.
05Should you use Make or n8n for FoundationX?
It depends on the tool your team already uses. On Make, FoundationX comes with 18 modules plus Make an API Call and works from the Free plan. The same app may also exist as an n8n node, so check what each side offers for the actions you need, then pick the editor you are more comfortable with. The comparison page on this site lays out the general differences. Whatever you choose, everything on this page describes the Make side of the integration only.
Same platform

Other docs you might need on this stack.

Browse all integrations