Resources · Make integration

Yeastar Contacts Make integrationAutomate Yeastar Contacts with Make.

Tired of retyping the same caller details into your phone system? The Yeastar Contacts Make integration gives you 4 modules: 3 actions and 1 search. This page is for ops teams who own the phonebook, and it walks you through connecting the account and building a first contact sync.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Yeastar Contacts Make integration do for you?

The Yeastar Contacts Make integration links your Yeastar contact list to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as an action or a search. Here, those bricks let you write, read and remove contacts without opening Yeastar.

A phonebook that follows your CRM. A deal is won or a new customer signs up in another tool, and Create or Update a Contact puts that person in Yeastar Contacts, so the next inbound call shows a name instead of a bare number.

A clean exit for departed customers. When an account closes elsewhere, Delete a Contact removes the matching entry and your agents stop seeing stale records.

An export for your other tools. List all Contacts hands every contact to the next module as a separate bundle (one item passed along the scenario), ready to feed a spreadsheet or a mailing tool.

What Make does not give you here: the app has no trigger, so Yeastar Contacts never starts a scenario by itself. You start it from another app or from a schedule. Make also flags its own Yeastar Contacts documentation as AI-generated, so check anything critical with Yeastar before you rely on it. The same app often has a node in n8n too; the n8n vs Make comparison lays out the differences between the two tools. To go further, the Make training covers scenario building from scratch, and the Make pricing guide explains how operations are counted.

Connect

How do you connect Yeastar Contacts to Make?

  1. 01

    Get your API Key

    Make signs in to Yeastar Contacts with an API Key, so you need an active account first. The doc points to the API section or Developer Settings of your dashboard: generate a key under API Key if none exists, then copy it somewhere safe.

  2. 02

    Open the connection window

    In a scenario, add any Yeastar Contacts module and click Create a connection. A connection is your account linked to Make once and reused by every module of the app. Give it a clear label in Connection name if you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API Key you copied, or follow the instructions Make shows on screen, and confirm. The connection now appears in the module's dropdown, and the other Yeastar Contacts modules can pick it without asking for the key again.

First scenario

Build your first scenario with Yeastar Contacts

GoalWhen a new customer lands in your CRM or form tool, Make adds or refreshes that person in Yeastar Contacts.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module decides when everything starts, and Yeastar Contacts has no trigger of its own.

  2. 02

    Pick the starting app

    Search for the app where your new customers first appear, such as your CRM or your form tool, choose its module that returns new records and connect that account.

  3. 03

    Add Create or Update a Contact

    Click the + on the right of the first module, search for Yeastar Contacts and pick Create or Update a Contact. Select your connection, then map the contact details coming from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received, so you can open Yeastar Contacts and confirm the right person was written.

  5. 05

    Schedule and switch on

    Click the clock on the first module to set how often Make checks for new customers; a new scenario runs every 15 minutes by default. Then turn the scenario on.

Modules

What each Yeastar Contacts module does

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

Yeastar Contacts1

Create or Update a Contact

ActionIn the docs only

You get one module that writes a person into your Yeastar phonebook, whether the entry already exists or not, so a sync never needs a separate branch for new and known callers.

When to use it
a customer is created or edited in your CRM and your agents should see the fresh details on the next call.
Watch out
Make's documentation for this app names no fields, so run it once on a test record and check the result in Yeastar before mapping real data.
Yeastar Contacts2

Delete a Contact

ActionIn the docs only

This module takes an entry out of Yeastar Contacts, which keeps the list your team dials from free of people you no longer work with.

When to use it
an account is closed or a customer asks to be forgotten in another tool, and the phonebook should follow.
Watch out
treat every deletion as final, so place a filter before it and test with Run once on a dummy contact first.
Yeastar Contacts3

List all Contacts

SearchIn the docs only

With this search you pull the whole contact list out of Yeastar, one bundle per person, ready for the next module to copy, compare or count.

When to use it
you want a backup in a spreadsheet or need to check which callers are missing from your CRM.
Watch out
every returned contact goes through the following modules one by one, and each of those executions is an operation counted on your Make plan.
Yeastar Contacts4

Make an API Call

ActionIn the docs only

Here you reach any endpoint of the Yeastar Contacts API from your scenario, reusing the same connection, which covers what the three ready-made modules leave out.

When to use it
you need a request that Create or Update a Contact, Delete a Contact and List all Contacts do not offer.
Watch out
you have to know the endpoint and its parameters from Yeastar's API documentation, since Make builds no form for you here.
Need help

Need help automating Yeastar Contacts with Make?

A person reads every message.

FAQ

Yeastar Contacts and Make: common questions

01Is the Yeastar Contacts Make integration free?
Yes, Yeastar Contacts is a standard app, so it works on the Make Free plan. That plan gives you 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, lift the cap on active scenarios and count usage in credits per month. Your Yeastar subscription is a separate matter that this page does not cover.
02What does the Yeastar Contacts Make connection require?
You need an active Yeastar Contacts account and an API Key. Generate the key from the API section or Developer Settings of your account dashboard, copy it, then add any Yeastar Contacts module in Make and click Create a connection. Naming the connection is optional but handy when several accounts coexist. Paste the key or follow the on-screen instructions, and every Yeastar Contacts module in your scenarios can reuse that connection afterwards.
03Can Yeastar Contacts start a Make scenario on its own?
No, the app has no trigger module, neither scheduled nor instant. A scenario that uses Yeastar Contacts therefore starts elsewhere: on a trigger from another app, such as a CRM or a form tool, or on Make's own schedule, which runs a new scenario every 15 minutes by default. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs, while paid plans go down to 1 minute. Pick the starting point that matches the moment your contact data changes.
04What if a Yeastar Contacts module is missing in Make?
It depends on the request, but Make an API Call usually covers it. That module calls any endpoint of the Yeastar Contacts API with the connection you already set up, so you are not limited to Create or Update a Contact, Delete a Contact and List all Contacts. You will need Yeastar's API reference to fill it in. Also keep in mind that Make labels its own documentation for this app as AI-generated, so confirm important behavior directly with Yeastar.
05Is Make or n8n better suited to Yeastar Contacts?
It depends on where the rest of your automations already live. In Make you get four ready-made modules plus Make an API Call, a visual editor and the Free plan to test the setup. Many apps also have an n8n node, so check whether one exists for Yeastar Contacts before comparing. Pick the tool your team already maintains, because a contact sync is easier to keep healthy when it sits next to the scenarios that feed it.