Resources · Make integration

ChatSonic Make integrationAutomate ChatSonic with Make.

What if ChatSonic answered the questions your other apps collect, without anyone copying and pasting? The ChatSonic Make integration has 2 action modules, available on every plan. This guide links your Writesonic API key, then builds a first scenario that sends a question and passes the reply along.

Try the ChatSonic integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the ChatSonic Make integration let you automate?

The ChatSonic Make integration lets Make send a question to ChatSonic and hand the answer to the next step of an automation. In Make, that automation is called a scenario: a chain of modules, where each module is one brick, like reading a form or asking ChatSonic. You wire it once, and questions stop needing a human in the middle.

ChatSonic has no trigger in Make, so something else starts the scenario: another app, or the schedule Make sets on the first module. From there, three setups cover most needs.

Draft a reply to every support ticket. A helpdesk module picks up the new ticket, Ask to Chatsonic receives its text as a question, and the answer lands as an internal note your agent reviews before sending.

Turn a form entry into a first draft. Someone fills in a brief on a site built with a form tool such as the one in our 123FormBuilder Make integration guide; ChatSonic writes a starting text and a chat or email module delivers it.

Reach an endpoint the listed module skips. Make an API Call calls any part of the ChatSonic API with the same connection, useful when the question format you need goes beyond what Ask to Chatsonic offers.

Know the limits. Make's documentation for this app gives no quota and no field list, and flags that its page is AI-generated from ChatSonic's own docs, so check anything important with ChatSonic. If you are weighing another tool for the same job, the n8n vs Make comparison lays out the criteria, and Make pricing explains how operations are counted.

Connect

How do you connect ChatSonic to Make?

  1. 01

    Grab your API key in ChatSonic

    You need an active Writesonic account. In ChatSonic, hover over your profile picture at the top right, open API Dashboard, flip the switch that activates the API, then copy the key that appears on screen.

  2. 02

    Open the connection window in Make

    Add a ChatSonic module to your scenario and click Create a connection. A connection is your ChatSonic account linked to Make once; both modules reuse it afterward. You can type a label in Connection name if you like.

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field, or follow the instructions Make shows on screen, then save. The connection now shows up in the module and you are ready to fill in the question.

First scenario

Build your first scenario with ChatSonic

GoalWhen a new entry arrives in another app, Make asks ChatSonic about it and passes the answer on.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Pick the app that holds your questions, such as a form or helpdesk, and its module that reads new entries.

  2. 02

    Add Ask to Chatsonic

    Click the + to the right of that first module, search for ChatSonic and choose Ask to Chatsonic. Select the connection you created, or click Create a connection now.

  3. 03

    Map the question

    In the module fields, map the text coming from the first module, for instance the body of the ticket. Each item passed between modules is a bundle: one ticket, one form entry.

  4. 04

    Test with Run once

    Click Run once to run the scenario a single time. Then look at the bundles each module received and check that ChatSonic got the right question.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, which is every 15 minutes by default, then switch the scenario on. Add a module after ChatSonic to send the answer where your team reads it.

Modules

What can ChatSonic do in Make?

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

ChatSonic1

Ask to Chatsonic

Action

In Make“Asks your questions to chatsonic.”

Gets you an answer from ChatSonic without opening it: the module sends a question built from your data and returns the reply as a bundle the next module can use.

When to use it
a support ticket or a form brief comes in and you want a first draft ready before anyone reads it.
Watch out
each run counts as an operation, one execution of the module on your Make plan, so test on a single item with Run once before switching the scenario on.
ChatSonic2

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Opens the rest of the ChatSonic API to your scenario: you pick the endpoint yourself and the module sends an authorized request with the connection you already set up.

When to use it
Ask to Chatsonic does not cover the request you have in mind and ChatSonic's API documentation lists an endpoint that does.
Watch out
Make gives no field list for this app, so you build the request from ChatSonic's own documentation and should verify it there first.
Need help

Need help automating ChatSonic with Make?

A person reads every message.

FAQ

ChatSonic and Make: frequent questions

01Is the ChatSonic Make integration free?
Yes, on the Make side. ChatSonic is a standard app, so it works on the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, and 5 minutes per execution. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run. Your ChatSonic subscription is separate: you need an active Writesonic account with API access, and its pricing is set by ChatSonic, not by Make.
02What do you need to connect ChatSonic to Make?
An active Writesonic account and a ChatSonic API key. To get the key, hover over your profile picture in ChatSonic, open API Dashboard, turn on the API switch and copy the key shown. In Make, add a ChatSonic module, click Create a connection, optionally name it, then paste the key. That single connection serves both modules of the app, so you only set it up once per account and pick it from the list in every later scenario.
03Does ChatSonic trigger a Make scenario in real time?
No, because ChatSonic has no trigger module in Make. A scenario that uses it has to start another way: with a trigger from a different app, for instance a new form entry or a new ticket, or with the schedule Make puts on the first module, every 15 minutes by default on a new scenario. ChatSonic then runs as an action step inside that flow, answering whatever the earlier module hands it.
04What if the ChatSonic module you need is missing in Make?
Use Make an API Call. It is listed among the ChatSonic modules and can call any endpoint of the ChatSonic API with the connection you already created, so you are not stuck with Ask to Chatsonic alone. Make's documentation for this app gives no field list and no documented limit, and notes that its page is AI-generated from ChatSonic's docs. Check the endpoint in ChatSonic's own API documentation before you build the request, and contact ChatSonic directly with vendor questions.
05Should you use Make or n8n with ChatSonic?
It depends on the tool your team already runs. Make gives ChatSonic 2 modules here: Ask to Chatsonic for questions and Make an API Call for everything else in the API, both on the Free plan. The same app often has a node in n8n too, so check what that node covers before deciding. Base the choice on the modules each side offers for your use case and on where your other automations already live, rather than on a general ranking.
Same platform

Other docs you might need on this stack.

Browse all integrations