Resources · Make integration

Charlie Lounge Make integrationAutomate Charlie Lounge with Make.

Can Make talk to Charlie Lounge without a line of code? Yes: the Charlie Lounge Make integration gives you 3 action modules and no trigger. This page explains each one, links your account and walks you through a first scenario you can test right away.

Try the Charlie Lounge integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Charlie Lounge Make integration do for you?

The Charlie Lounge Make integration lets a Make scenario, the automation you build in Make, act on your Charlie Lounge account. It offers three actions: send a message to an assistant, create a completion, or call any other part of the Charlie Lounge API. There is no trigger, so another app or a schedule starts the flow.

Forward incoming requests to an assistant. A form, an inbox or a CRM from another app hands Make a new item, and Create Message To an Assistant passes it on to Charlie Lounge. Each module is one brick of the scenario, and the item it carries is called a bundle.

Produce a completion from your own data. Place Create a Completion after the module that supplies the text, then map that text into it. Make then sends the result to the next module you add.

Reach what the listed modules leave out. Make an API Call calls any endpoint of the Charlie Lounge API with the same connection, which is handy when the two named actions are not enough.

Be aware of one limit before you plan too far: Make's own documentation for Charlie Lounge is marked as limited, because little public information exists about the app. Expect to test each module with Run once and read what comes back. If something breaks, the Make troubleshooting guide covers the usual errors, and the Make training teaches the editor step by step. Weighing another tool? The n8n vs Make comparison sets out the criteria.

Connect

How do you connect Charlie Lounge to Make?

  1. 01

    Open a Charlie Lounge module

    Add any Charlie Lounge module to your scenario, then click Create a connection. A connection is your Charlie Lounge account linked to Make once and reused by every module of the app.

  2. 02

    Name the connection

    This step is optional, but a clear name helps when several people or several accounts share the same Make organization. Pick something that tells you which Charlie Lounge account sits behind it.

  3. 03

    Authorize and save

    Depending on what Charlie Lounge asks for, either approve Make on the app's own page or paste the key the app gives you. Then click Save, and Make can now read and act on the account.

First scenario

Your first scenario with Charlie Lounge

GoalWhen another app hands Make a new request, Make sends it as a message to a Charlie Lounge assistant.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas to place the first module.

  2. 02

    Pick the starting app

    Charlie Lounge has no trigger, so choose the app where requests arrive, such as your form tool or inbox, and set up its module and connection.

  3. 03

    Add the Charlie Lounge action

    Click the + on the right of that module, search for Charlie Lounge and choose Create Message To an Assistant. Select your connection or create one.

  4. 04

    Map the request text

    Fill the module fields and map the text from the first module into the message. Run the first module once if you want real data to pick from.

  5. 05

    Test with Run once

    Click Run once to execute the scenario a single time, then open the bubble above each module to read the bundles it received and sent.

  6. 06

    Schedule and switch on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on so it keeps running without you.

Modules

What each Charlie Lounge module does

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

Charlie Lounge1

Create Message To an Assistant

ActionIn the docs only

You get a message delivered to one of your Charlie Lounge assistants, built from data another module produced earlier in the scenario.

When to use it
a customer request lands in a form or an inbox and you want the assistant to receive it without anyone copying and pasting.
Watch out
Make publishes no field list for this module, so run it once and check the output before you connect anything after it.
Charlie Lounge2

Create a Completion

ActionIn the docs only

This action hands you a completion from Charlie Lounge, which the next module can store, send or reuse as a regular bundle.

When to use it
pick it over the assistant message when you want a result back in the scenario rather than a message handed to an assistant.
Watch out
each run counts as one operation, the unit Make bills on your plan, so filter the incoming items first if only some deserve a completion.
Charlie Lounge3

Make an API Call

ActionIn the docs only

With this module you can reach any endpoint of the Charlie Lounge API while reusing the connection you already created, so no second login is needed.

When to use it
the two named actions do not cover your need, for example an operation the Charlie Lounge API offers but no module lists.
Watch out
since Make's documentation for this app is limited, you will need the endpoint details from Charlie Lounge itself before you fill this module in.
Need help

Need help automating Charlie Lounge with Make?

A person reads every message.

FAQ

Charlie Lounge and Make: common questions

01Is the Charlie Lounge Make integration free?
Yes, on the Make side. Charlie Lounge is a standard app, so its modules work from the Free plan onward. The Free plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, up to 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Your Charlie Lounge subscription is a separate matter that this page does not cover.
02What does connecting Charlie Lounge to Make require?
A Charlie Lounge account and a Make account are the starting point. Make's documentation lists no specific prerequisite for this app and gives no official connection steps, so the generic flow applies: add a Charlie Lounge module, click Create a connection, optionally name it, authorize Make on the app's page or paste the key Charlie Lounge provides, then click Save. That single connection then serves all three modules, including Make an API Call.
03Does the Charlie Lounge Make integration react in real time?
No, because Charlie Lounge has no trigger module in Make. The scenario has to start elsewhere. You can open it with a trigger from another app, such as the tool where requests arrive, and place the Charlie Lounge action after it. You can also rely on the schedule of the first module, which runs every 15 minutes by default on a new scenario. The Free plan keeps at least 15 minutes between two scheduled runs; paid plans go down to 1 minute.
04What if a Charlie Lounge module is missing in Make?
Use Make an API Call. It calls any endpoint of the Charlie Lounge API with the connection you already set up, so it covers what Create Message To an Assistant and Create a Completion leave out. Keep in mind that Make marks its Charlie Lounge documentation as limited because little public information exists about the app. You will likely need the API reference from Charlie Lounge to know which endpoint to call and what it expects.
05Make or n8n for Charlie Lounge automation?
It depends on the tool your team already works in. On Make, Charlie Lounge offers 3 action modules, one of them a generic API call, and no trigger, so another app or a schedule has to start each scenario. Before choosing, check whether n8n offers a node for this app and compare what each side lets you do with it. Nothing in the documentation of either tool ranks one above the other for Charlie Lounge.
Same platform

Other docs you might need on this stack.

Browse all integrations