Automate xAI With Make: 3 Modules to Write and Draw, No Code

What you can automate

What can the xAI Make integration do for you?

The xAI Make integration links your xAI account to Make, a no-code tool where you build a scenario: the automation itself, a chain of modules that runs on a schedule or when an app calls Make. xAI brings three modules to that chain, so a prompt can turn into written text or an image without you copying anything by hand.

Replies drafted before you open the inbox. A support request lands in your help desk, another app hands the message to Create a completion, and the draft answer goes back as a note. Your agents edit instead of starting from a blank page.

Visuals that follow the copy. A marketing team adds a product to a spreadsheet; Create a completion writes the short description, then Generate an image produces a picture from a prompt built with that description. Both land in the same row.

Anything the listed modules skip. Make an API call reaches other parts of the xAI API with the connection you already set up, which keeps you inside one scenario when a need falls outside the two ready-made modules.

Keep in mind that xAI has no trigger in Make: it never starts a scenario itself. Something else does, a schedule or another app, and xAI works in the middle. If you also work with n8n, the xAI n8n integration covers the same app, and n8n vs Make helps you pick. To see how Make counts usage, read Make pricing.

Connect

How do you connect xAI to Make?

01
Add an xAI module
In your scenario, click the + and search for xAI. Pick any of its modules, then click Create a connection. A connection is your xAI account linked to Make once, and every xAI module reuses it afterward.
02
Name the connection and authorize
Give the connection a name you will recognize later, for instance the project it serves. Then authorize Make on the xAI page that opens, or paste the key xAI gives you if Make asks for one.
03
Save and check
Click Save. The module now shows your connection in its drop-down, and the fields you need to fill appear below it. If the list stays empty, open the connection again and repeat the authorization.

First scenario

Your first scenario with xAI and Make

GoalWhen a new entry arrives from another app, Make asks xAI for a short text, then turns that text into an image.

01
Create the scenario
Open the Scenarios page, create a new scenario and click the + to add the first module. Choose the app where your entries arrive, such as your form tool, and connect it.
02
Add Create a completion
Click the + on the right of that first module, search for xAI and pick Create a completion. Create the xAI connection if this is your first xAI module.
03
Write the prompt with mapped data
Fill the module fields. Map data from the first module into your prompt, for example the product name from the form, so each run writes about the entry it just received.
04
Add Generate an image
Click the + again and choose Generate an image. Build its prompt from the text the completion returned, so the picture matches the words.
05
Test with Run once
Click Run once. Make runs the scenario one time; open each module to read the bundles it received, each bundle being one item passed from module to module.
06
Schedule and switch on
Open the clock on the first module to set Scheduling. A new scenario checks every 15 minutes by default. Then switch the scenario on and let it work.

Modules

What the xAI modules do

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

xAI1

Create a completion

Action

In Make“Creates a chat or prompt completion.”

You get text written by xAI from a prompt or a chat exchange you send, ready to pass to the next module as a reply, a summary or a description.

When to use it

a new support ticket or product row reaches the scenario and you want a first draft attached to it, without anyone typing.

Watch out

each call counts as an operation on your Make plan, so send it only the entries that truly need a draft, not every item your first module returns.

xAI2

Make an API call

Action

In Make“Performs an arbitrary authorized API call.”

This one hands you the rest of the xAI API: you call an endpoint of your choice, and Make sends it through the xAI connection you already created.

When to use it

the two ready-made modules do not cover what you need, and you would rather stay in the same scenario than build a separate tool.

Watch out

you describe the request yourself here, so keep the xAI API reference open while you write it.

xAI3

Generate an image

Search

In Make“Generates an image based on a prompt.”

With this module a written prompt comes back as an image, which the next module can store, attach to a record or post somewhere else.

When to use it

a new product or article already has text in the scenario and needs a matching visual right away.

Watch out

Make files it as a search, so it can return zero, one or several bundles; check in Run once how many come out before adding the step that saves them.

Need help

Need help automating xAI with Make?

A person reads every message.

FAQ

Questions about the xAI Make integration

01Is the xAI Make integration free?

Yes, on the Make side. xAI is a standard app, so it works from the Free plan. That plan allows 2 active scenarios, a scheduled run every 15 minutes at the shortest, 5 minutes of execution per run and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Usage on every plan is counted in operations, one per module and per bundle. Your xAI account is a separate matter handled with xAI directly.

02What do you need to connect xAI to Make?

An xAI account and a Make account are enough to start. Add any xAI module, click Create a connection, give it a name, then either authorize Make on the xAI page or paste the key xAI provides, and click Save. The official docs list no extra requirement. The connection is created once and every xAI module in your scenarios reuses it, so you never repeat the step for each module.

03Does the xAI Make integration react in real time?

No, because xAI has no trigger in Make and cannot start a scenario on its own. The scenario starts from something else: a trigger of another app, such as a form or a help desk, or the schedule set on the first module, which is every 15 minutes by default. Once that first module fires, the xAI modules run right after it within the same execution, so the delay comes from the starting point, not from xAI.

04What if the xAI module you need is missing in Make?

Use Make an API call. It reaches any endpoint of the xAI API with the connection you already have, so you can cover what Create a completion and Generate an image leave out without leaving your scenario. You write the request yourself, so the xAI API reference becomes your guide. The official Make docs for xAI publish no numeric limit, and when a scenario fails, the error shown by Run once is the first place to look.

05Should you use Make or n8n for xAI?

It depends on the tool your team already uses. xAI has 3 modules in Make, including Make an API call for anything else, and n8n also has an xAI node. Pick the platform where your other apps and scenarios already live, so data does not have to travel between two tools. If you are starting from scratch, compare how each editor feels on a small test with the same prompt before committing.

Add an xAI module

Name the connection and authorize

Save and check

Create the scenario

Add Create a completion

Write the prompt with mapped data

Add Generate an image

Test with Run once

Schedule and switch on

Need help automating xAI with Make?