Resources · Make integration

TypeFore Make integrationAutomate TypeFore with Make.

Can Make feed TypeFore without a single line of code? Yes. The TypeFore Make integration gives you 4 action modules to send, fetch and update communications. This guide connects your account, then walks you through a first scenario.

Try the TypeFore integration on MakeSee the 4 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the TypeFore Make integration let you automate?

The TypeFore Make integration links your TypeFore account to Make, a tool where you build a scenario: an automation made of modules, each module being one brick that acts on one app. TypeFore brings 4 action modules. They push communications into TypeFore, read them back and change them, while another app or a schedule decides when the scenario starts.

Every captured message ends up in TypeFore. Put the trigger of your form or inbox tool first, then Ingest communication: each item it hands over, called a bundle in Make, becomes a communication in TypeFore.

One record stays current instead of three copies. When a later event changes an exchange, Update communication edits the existing communication rather than creating a new one.

The full content travels to the next tool. Get communication loads a communication into the scenario so a following module can reuse its data.

Know the limits before you start. TypeFore has no trigger in Make, so it cannot start a scenario by itself, and the Make documentation for this app is limited: it lists no prerequisites and no field details. For anything the modules miss, Make an API call reaches the TypeFore API with the same connection. The same app sometimes exists as an n8n node too; the n8n vs Make comparison helps you pick a platform, and the Make review or our Make training cover the editor in depth.

Connect

How do you connect TypeFore to Make?

  1. 01

    Add a TypeFore module

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

  2. 02

    Name it and authorize Make

    Give the connection a name if you like, for example the workspace it belongs to. Then either approve Make on the TypeFore authorization page or paste the key TypeFore gives you, depending on what the window asks for.

  3. 03

    Save the connection

    Click Save. Back in the module, Make can now read what your account exposes, so the fields fill with choices you pick from a list instead of typing values by hand.

First scenario

Build your first scenario with TypeFore

GoalWhen a new message is captured in another app, Make sends it to TypeFore as a communication.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle. The first module comes from the app where messages arrive, since TypeFore has no trigger of its own.

  2. 02

    Add Ingest communication

    Click the + on the right of that first module, search for TypeFore and choose Ingest communication. Pick the connection you created, or click Add to make it now.

  3. 03

    Map the incoming data

    Fill the module fields by clicking into them and choosing values from the previous module. The text, sender or answer captured upstream flows straight into the new communication.

  4. 04

    Test it with Run once

    Click Run once, then trigger a real message in the source app. Open the bubble above each module to read the bundles it received and confirm TypeFore got the communication.

  5. 05

    Schedule and switch on

    Set the schedule on the first module with the clock icon. A new scenario checks every 15 minutes by default. Then flip the switch to turn the scenario on.

Modules

What can TypeFore do in Make?

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

TypeFore1

Get communication

ActionIn the docs only

Going by its name, since Make gives no description, Get communication loads one communication stored in TypeFore into your scenario, so the modules after it can read its data and send it elsewhere. It works on a single item: one bundle in, one bundle out.

When to use it
an earlier module gave you the reference of a communication and you need its content before passing it on.
Watch out
the Make documentation says little about this app, so inspect the fields Make offers once connected before mapping anything.
TypeFore2

Ingest communication

ActionIn the docs only

Messages collected by your other tools land in TypeFore thanks to Ingest communication, which, judging by its name, creates a new communication for each bundle it receives. It is the module that fills TypeFore from the outside.

When to use it
right after the trigger of the app where the conversation starts, such as a form tool or an inbox.
Watch out
every bundle costs one operation, meaning one execution counted on your plan, so a trigger returning many items ingests each one separately.
TypeFore3

Make an API call

ActionIn the docs only

With Make an API call, any endpoint of the TypeFore API stays within reach, using the connection you already have. It covers whatever the three dedicated modules leave out, without a second login.

When to use it
you need a TypeFore action that has no module of its own in Make.
Watch out
you build the request yourself and the Make documentation for TypeFore is thin, so test the call with Run once before the scenario goes live.
TypeFore4

Update communication

ActionIn the docs only

A single tidy record per exchange is what Update communication should give you: its name says it edits a communication that already exists in TypeFore instead of adding a duplicate.

When to use it
something about an exchange changes after the first ingest, like a reply that comes in later through another tool, and TypeFore must show it.
Watch out
the module has to know which communication to edit, so map its reference from an earlier module rather than typing it by hand.
Need help

Need help automating TypeFore with Make?

A person reads every message.

FAQ

TypeFore and Make: common questions

01Is the TypeFore Make integration free?
Yes. TypeFore is a standard app in Make, so it works from the Free plan onward, like the 3,000+ standard apps. The Free plan keeps 2 active scenarios, waits at least 15 minutes between two scheduled runs, stops a run after 5 minutes, and handles files up to 5 MB with 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in operations each month.
02What do you need to connect TypeFore to Make?
A TypeFore account and a Make account are enough to begin. The Make documentation lists no other prerequisite for this app. Add any TypeFore module, click Create a connection, name it if you want, then authorize Make on the TypeFore page or paste the key TypeFore provides, and click Save. The connection is stored once and every TypeFore module in your scenarios reuses it. If the window asks for something you cannot find, check with whoever manages your TypeFore account.
03Can TypeFore start a Make scenario in real time?
No. TypeFore has no trigger module in Make, so it cannot start a scenario on its own. You start the flow another way. Either put the trigger of another app first, and if that trigger is instant, meaning the app calls Make through a webhook, the scenario runs as soon as the event happens. Or run the scenario on a schedule set with the clock on the first module, every 15 minutes by default, and let the TypeFore modules act at each run.
04What if the TypeFore module you need is missing in Make?
Use Make an API call. This module can call any endpoint of the TypeFore API from your scenario, with the same connection as the other modules, so you are not limited to the 4 modules listed. Keep in mind that the Make documentation for TypeFore is limited and gives no field details, so build the request carefully and test it with Run once. If that still does not fit, another app or form tool may cover the step before the data reaches TypeFore.
05Should you use Make or n8n for TypeFore?
It depends on the platform your team already works in. In Make, TypeFore offers 4 action modules plus access to its API through Make an API call, and no trigger, so another app or a schedule starts the flow. Many apps also have a node in n8n, so check whether TypeFore is one of them before you decide. Neither tool is ranked here: compare the modules each one offers for TypeFore against the steps your process actually needs, then choose.
Same platform

Other docs you might need on this stack.

Browse all integrations