Resources · Make integration

RelationCity Make integrationAutomate RelationCity with Make.

Can Make text your customers and tidy your RelationCity contacts while you work on something else? Yes: the RelationCity Make integration offers 20 modules, 18 actions and 2 searches, with no trigger. This guide links your account, then walks you through a first scenario.

Try the RelationCity integration on MakeSee the 20 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the RelationCity Make integration let you automate?

The RelationCity Make integration links your RelationCity account to Make, the no-code tool where you build a scenario: a chain of modules that runs on a schedule or when another app calls Make. Each module is one brick of that chain. Once connected, your contacts, SMS campaigns, texts and emails in RelationCity follow what happens in your other tools, with no copy and paste.

A welcome text for every new lead. Create a Contact files the person who just filled in your form, then Send a SMS using a SMS Template greets them with wording your marketing team already approved.

A promotion that stops on its own. When your online shop reports an item out of stock, Pause SMS Campaign freezes the offer, and Resume a SMS Campaign restarts it once the item is back. Get Status of an SMS Campaign can post the state in your team chat.

Contact lists that match your CRM. Fetch a Contact by Email checks whether a record exists, Update a Contact refreshes it, and Delete a Contact by Phone Number removes people who opted out through another channel.

What Make does not cover here: RelationCity has no trigger, so it never starts a scenario by itself, and Make warns that its documentation for this app is limited. Anything the listed modules miss goes through Make an API Call. RelationCity may also be available in n8n; the n8n vs Make comparison lays out how to choose, and Make pricing explains how operations are counted. For a guided start, the Make training covers the editor from scratch.

Connect

How do you connect RelationCity to Make?

  1. 01

    Add a RelationCity module

    In your scenario, click the + and search for RelationCity. Pick any module, Create a Contact for instance, then click Create a connection. A connection is your RelationCity account linked to Make once; every RelationCity module reuses it.

  2. 02

    Name the connection

    Give it a clear name if you plan to link more than one RelationCity account, one per brand for example. The step is optional, yet a named connection is much easier to spot when a scenario stops and you need to find out why.

  3. 03

    Authorize and save

    Make then asks you either to approve access on a RelationCity page or to paste the key RelationCity gives you. The official doc does not say which of the two applies. Fill in the screen Make shows, then click Save.

First scenario

Your first RelationCity scenario in Make

GoalWhen a new lead arrives through your form tool, Make creates the contact in RelationCity and sends a welcome SMS from a template.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. RelationCity has no trigger, so start with the app where your leads land, such as your form tool.

  2. 02

    Add Create a Contact

    Click the + on the right of the first module, search for RelationCity and pick Create a Contact. Link your account with Create a connection, then map the lead details coming from the form.

  3. 03

    Add the template SMS

    Add Send a SMS using a SMS Template after it. With the connection in place, Make lists what it can read in RelationCity, so you choose your welcome template instead of typing the text.

  4. 04

    Test with Run once

    Click Run once with a test lead that carries your own phone number. Then read the bundles each module received: a bundle is one item moving from module to module, here one lead.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan. Switch the scenario on and new leads get their text.

Modules

The 20 RelationCity modules in Make

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

RelationCity1

Create a Contact

ActionIn the docs only

Adds a new person to your RelationCity contact base, so every lead collected elsewhere is ready for your SMS campaigns without manual entry.

When to use it
right after a form, a shop or a CRM hands Make a new customer, and before any module that sends a message.
Watch out
the doc says nothing about duplicates, so place Fetch a Contact by Email in front of it when the same person can come in twice.
RelationCity2

Create a SMS Campaign

ActionIn the docs only

Sets up a fresh SMS campaign in RelationCity from your scenario, instead of building it by hand in the app for every launch.

When to use it
a new promotion added to your catalog, or an event published in your planning tool, should turn into a campaign ready to go.
Watch out
the doc lists no required settings, so click Run once and open the campaign inside RelationCity before switching the scenario on.
RelationCity3

Create a SMS Campaign Tag

ActionIn the docs only

Gives you a new label for sorting SMS campaigns, which keeps reporting readable once dozens of campaigns pile up in the account.

When to use it
a new client, region or product line in your records needs its own label before its first campaign goes out.
Watch out
the module runs once per bundle, so if several items reach it, it tries to create the tag several times; keep it ahead of any iterator (the module that splits a list into separate items).
RelationCity4

Delete a Contact by ID

ActionIn the docs only

Removes one contact for good when you already hold its RelationCity ID, keeping your list free of people who asked to leave.

When to use it
an unsubscribe request comes through your help desk and an earlier Fetch module returned the ID of that person.
Watch out
a delete cannot be undone, so test with Run once on a dummy contact you created for the purpose.
RelationCity5

Delete a Contact by Phone Number

ActionIn the docs only

Wipes a contact using only the phone number, which saves a lookup step when your other app never stored the RelationCity ID.

When to use it
a customer opts out on another channel and the number is the only link between that tool and RelationCity; prefer the ID version when you have the ID.
Watch out
nothing brings the contact back, so first check with a test that the number, written the way your other app writes it, targets the right person.
RelationCity6

Fetch Contacts with a Specific Tag

ActionIn the docs only

Pulls back the contacts that carry one tag, so a single segment of your audience can feed the rest of the scenario.

When to use it
you want to copy your VIP segment into a spreadsheet, or hand it to an ads tool for a matching audience.
Watch out
Make lists it as an action, yet its name promises several contacts; read what a Run once returns before chaining a module that expects one item.
RelationCity7

Fetch a Contact by Email

ActionIn the docs only

Finds the RelationCity record behind an email address, which tells you whether a lead already exists before you create anything.

When to use it
a newsletter signup or a webinar registration arrives and you want to avoid entering the same person twice.
Watch out
run a test with an address that is not in RelationCity and look at the bundle you get, so the next module handles the empty case.
RelationCity8

Fetch a Contact by ID

ActionIn the docs only

Reads one contact straight from its RelationCity ID, the most direct lookup when an earlier module already gave you that identifier.

When to use it
a previous step stored the ID and you need the rest of the record to personalize a text or update another tool.
Watch out
the ID is the one RelationCity assigns; a customer number from your shop or your CRM will not match it.
RelationCity9

Fetch a Contact by Phone Number

ActionIn the docs only

Looks up a contact from the number you text, useful when your call software or booking tool only knows the phone.

When to use it
a booking app sends Make a phone number and you want the matching RelationCity profile before updating it.
Watch out
check with Run once that the number, as your other app formats it, really finds the contact you expect.
RelationCity10

Get Status of an SMS Campaign

ActionIn the docs only

Tells you where a campaign stands without anyone opening RelationCity, so your scenario can report on it or choose what happens next.

When to use it
after Create a SMS Campaign or Resume a SMS Campaign, to post the state in your team chat or a tracking sheet.
Watch out
the doc does not list the possible statuses, so read the bundle from a test before writing rules that depend on it.
RelationCity11

List Contact Tags

SearchIn the docs only

Returns the tags on your contact base, so the scenario picks the right one from real data instead of a label typed by hand.

When to use it
just before Fetch Contacts with a Specific Tag, to confirm the tag exists under the exact spelling RelationCity uses.
Watch out
as a search, it can return zero, one or several bundles, and every module after it runs once per tag, which adds operations.
RelationCity12

List SMS Transaction Prices

SearchIn the docs only

Lists the SMS transaction prices from your RelationCity account, handy for keeping an eye on sending costs from a spreadsheet.

When to use it
before a large Send a SMS to Recipients, so the finance team can see the prices in the sheet they already follow.
Watch out
the doc gives no detail on what each price bundle contains; read the output of a test before using it in any calculation.
RelationCity13

Make an API Call

ActionIn the docs only

Reaches any endpoint of the RelationCity API with the connection you already set up, your way out when no listed module fits.

When to use it
a feature you rely on in RelationCity has no dedicated module in Make.
Watch out
you need the RelationCity API documentation for the path and parameters, and Make offers little guidance of its own for this app.
RelationCity14

Pause SMS Campaign

ActionIn the docs only

Puts a running SMS campaign on hold from your scenario, so a problem spotted elsewhere stops the sending before more messages go out.

When to use it
a stock alert or a pricing error flagged in another tool should freeze the promotion straight away.
Watch out
pausing is not deleting; plan the matching Resume a SMS Campaign step, or the campaign stays frozen.
RelationCity15

Resume a SMS Campaign

ActionIn the docs only

Restarts a campaign you paused earlier, so sending picks up again without anyone logging in to RelationCity.

When to use it
the product is back in stock, or the corrected offer gets approved in your project tool.
Watch out
it needs to know which campaign to restart, so keep the campaign reference from the pause step somewhere your scenario can read, such as a spreadsheet.
RelationCity16

Send a SMS to Recipients

ActionIn the docs only

Sends a text to the numbers you give it, with wording your scenario builds from earlier data such as an order number or a date.

When to use it
an order ships, an appointment is confirmed or a payment fails; prefer it over the template module when the text changes each time.
Watch out
a Run once test sends a real SMS, so point it at your own number first.
RelationCity17

Send a SMS using a SMS Template

ActionIn the docs only

Uses a template already saved in RelationCity to send the SMS, so the approved wording stays identical from one message to the next.

When to use it
reminders and confirmations that marketing wrote once and does not want anyone editing inside Make.
Watch out
create the template in RelationCity first; Make can only offer the templates your connection is able to read.
RelationCity18

Send an Email

ActionIn the docs only

Emails a contact from RelationCity, which keeps texts and emails under one account instead of adding a separate mail app to the scenario.

When to use it
a customer has no mobile number on file, or the message needs more room than an SMS gives you.
Watch out
the doc says nothing about the sender or the layout, so send yourself a test with Run once before switching on.
RelationCity19

Update Sending Speed of an SMS Campaign

ActionIn the docs only

Changes how fast a campaign sends its messages, so replies and calls reach your team at a pace it can handle.

When to use it
your support desk reports a wave of calls after a campaign starts and asks for a slower flow.
Watch out
the doc does not give the accepted values; look at what Make shows in the module once the connection exists before mapping anything.
RelationCity20

Update a Contact

ActionIn the docs only

Edits an existing RelationCity contact with fresh data from another app, so your SMS lists never drift away from your CRM.

When to use it
a customer changes number or address in your CRM; choose it over Create a Contact once you know the person is already there.
Watch out
it acts on one known contact, so put a Fetch module in front of it to find which one.
Need help

Need help automating RelationCity with Make?

A person reads every message.

FAQ

RelationCity and Make: common questions

01Is the RelationCity Make integration free?
Yes. RelationCity is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, caps each run at 5 minutes, handles files up to 5 MB and includes 512 MB of data transfer. Every module run on one bundle counts as one operation on your plan. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, lift the limit on active scenarios and allow 40 minutes per run. RelationCity's own pricing is a separate matter to check in your RelationCity account.
02What do you need to connect RelationCity to Make?
A RelationCity account and a Make account; the Make documentation lists no other prerequisite. Add any RelationCity module, click Create a connection, name it if you like, then either approve Make on a RelationCity page or paste the key RelationCity provides, and click Save. The doc does not state which of the two methods RelationCity uses, since Make flags its documentation for this app as limited. The connection is made once and reused by all 20 modules.
03Does RelationCity trigger Make scenarios in real time?
No. RelationCity has no trigger in Make, scheduled or instant, so it cannot start a scenario by itself. You have two ways around it. Open the scenario with an instant trigger from another app, one that calls Make through a webhook as soon as something happens, such as a new form entry. Or set a schedule on the first module: every 15 minutes by default, 15 minutes at the shortest on the Free plan, down to 1 minute on paid plans. The RelationCity actions then follow in the chain.
04What if the RelationCity module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the RelationCity API with the connection you already have, so you are not limited to the 18 actions and 2 searches in the list. You will need RelationCity's own API documentation for the path and parameters, because Make says its documentation for this app is limited. If what you miss is a way to start the scenario rather than an action, pair RelationCity with a trigger from another app instead.
05Should you use Make or n8n for RelationCity?
It depends on the tool your team already runs and on what you need to cover. On Make, RelationCity gives you 20 modules without a trigger, plus Make an API Call for the rest, all built in the visual scenario editor. Apps like RelationCity often have an n8n node as well, so check whether one exists and what it covers before choosing. Compare the actions you actually need on each side, not the brand names, and pick the tool your team will maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations