Resources · Make integration

Pingmee Make integrationAutomate Pingmee with Make.

Can Make route your Pingmee conversations for you? The Pingmee Make integration gives you 13 modules: 2 triggers and 11 actions. This guide is for support and sales teams who live in Pingmee, and it walks you from the connection to a first working scenario.

Try the Pingmee integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Pingmee Make integration do?

The Pingmee Make integration links your Pingmee account to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something. Here the bricks watch new conversations and messages, then tag, assign, update customers or send templates for you.

Every new chat lands with the right person. Watch New Conversation spots the chat, then Assign Agents To Conversation hands it to someone on your team, so nobody has to sort the inbox by hand.

Messages get labeled as they come in. Pair Watch New Messages with Assign a Tag to a Conversation and your conversations carry a tag your team can filter on. Create Tag and Get Tags keep that list of labels tidy.

Your customer records stay current. When a form, a store or a CRM learns something new about a person, Create Customer or Update a Customer writes it into Pingmee, and Send a Template can follow up with a prepared message.

Be aware that Make itself says its documentation for Pingmee is limited, because there is not enough public information about the app. The module names are clear, but the fields behind them are only described inside the editor, so plan a test run before you trust a scenario. If you want a second opinion on the tool, read our Make review or learn the basics with Make training. Pingmee may also exist in n8n; n8n vs Make compares the two editors.

Connect

How do you connect Pingmee to Make?

  1. 01

    Open a Pingmee module

    In a scenario, add any Pingmee module and click Create a connection. A connection is your Pingmee account linked to Make once; every Pingmee module in every scenario reuses it afterwards.

  2. 02

    Name the connection

    Giving it a name is optional, but helpful when several people or several Pingmee workspaces share one Make account. A name like the team or the client keeps the right account easy to pick later.

  3. 03

    Authorize and save

    Depending on what Pingmee asks for, approve Make on the Pingmee page that opens or paste the key Pingmee gives you, then click Save. The module can now read your Pingmee data.

First scenario

Your first scenario: give each new conversation an owner

GoalWhen a new conversation starts in Pingmee, Make assigns an agent to it.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. This first module decides when everything else starts.

  2. 02

    Add the trigger

    Search for Pingmee, pick Watch New Conversation and link your account with Create a connection, or select the connection you already made.

  3. 03

    Add the assignment

    Click the + on the right of the trigger and choose Assign Agents To Conversation. Map the conversation coming from the trigger, then fill the agent fields the module shows you.

  4. 04

    Test with Run once

    Click Run once, then open a test chat in Pingmee if nothing shows up. Read the bundles each module received: a bundle is one item passed along, here one conversation.

  5. 05

    Schedule and switch on

    On the first module, set the schedule (every 15 minutes by default, 15 minutes at the shortest on the Free plan) and switch the scenario on. It now runs by itself.

Triggers

What can start a Pingmee scenario?

2 modules start a scenario when something happens in Pingmee. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pingmee as soon as it happens.

Pingmee1Watch New Conversation

Watch New Conversation

triggerIn the docs only

Watch New Conversation starts your scenario each time a fresh conversation appears in Pingmee, so the first contact with a customer can set off a routing or logging step without anyone watching the inbox.

How it fires
scheduled (inferred from the module name), Make checks Pingmee on the scenario's schedule, which is every 15 minutes for a new scenario, so new chats are picked up in batches rather than the second they open.
When to use it
you want every new chat assigned, tagged or copied into another tool as soon as it is picked up.
Watch out
Make lists this module without a description, so run it once on a live account and read the bundle before you map anything.
Pingmee2Watch New Messages

Watch New Messages

triggerIn the docs only

Watch New Messages hands your scenario each message that has arrived since the last check, which suits follow-ups inside conversations that are already open rather than only the first hello.

How it fires
scheduled (inferred from the module name), Make checks Pingmee on the scenario's schedule; the Free plan allows 15 minutes at the shortest between two checks, paid plans go down to 1 minute.
When to use it
a reply from a customer should add a tag, change a status or be pushed to a team channel.
Watch out
busy inboxes produce many bundles, and each module run on each bundle counts as one operation on your Make plan.
Modules

What can Make do in Pingmee?

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

Pingmee1

Assign Agents To Conversation

ActionIn the docs only

This module puts one or more agents in charge of a conversation, so the chat stops waiting in a shared queue and has a named owner on your team.

When to use it
right after Watch New Conversation, to route chats by language, product or region.
Watch out
pull the agent list with Get Agents first if you are not sure which values the field expects.
Pingmee2

Assign a Tag to a Conversation

ActionIn the docs only

Here a label gets pinned on a conversation, which lets your team filter the inbox or report on topics without reading every thread again.

When to use it
after a new message mentions a refund, a demo or a bug, to mark the chat for the right queue.
Watch out
the tag has to exist in Pingmee; create it beforehand with Create Tag if needed.
Pingmee3

Create Customer

ActionIn the docs only

Create Customer adds a new person to Pingmee from data another app already holds, so your agents see a known contact instead of an anonymous visitor.

When to use it
a lead fills a form or buys in your store and should exist in Pingmee before they write.
Watch out
running it twice for the same person can create a duplicate; use Update a Customer for someone already there.
Pingmee4

Create Tag

ActionIn the docs only

With Create Tag a brand new label appears in your Pingmee account, ready for Assign a Tag to a Conversation to use in the same scenario or later ones.

When to use it
a new campaign, product or event name should become a label without someone setting it up by hand.
Watch out
check the existing list with Get Tags first, otherwise you may end up with two tags that mean the same thing.
Pingmee5

Delete a Tag

ActionIn the docs only

Delete a Tag removes a label from Pingmee entirely, which keeps the tag list short once a campaign or a product line is over.

When to use it
a cleanup scenario retires labels that another tool marks as closed or archived.
Watch out
a deletion cannot be undone from Make, so test it on a throwaway tag with Run once before pointing it at real ones.
Pingmee6

Get Agents

ActionIn the docs only

Get Agents reads the agents of your Pingmee account and hands them to the next module, which saves you from typing names or IDs into an assignment by hand.

When to use it
just before Assign Agents To Conversation, when you pick the owner based on the data you receive.
Watch out
the documentation does not say what each result holds, so open the bundles after a Run once to see what you can map.
Pingmee7

Get Tags

ActionIn the docs only

Get Tags fetches the labels that already exist in Pingmee, so a scenario can check what is there before it creates, assigns or removes anything.

When to use it
ahead of Create Tag, to avoid a duplicate label, or to copy your tag list into a spreadsheet.
Watch out
like the other modules here, it has no official description; read its output once before you build filters on it.
Pingmee8

Send a Template

ActionIn the docs only

Send a Template pushes one of your prepared Pingmee messages to a customer, so a standard answer or reminder goes out without an agent typing it.

When to use it
an order ships, an appointment is booked or a form arrives in another app and the customer should hear about it.
Watch out
a message sent is sent, so aim your first tests at your own contact or a colleague's.
Pingmee9

Set a Status

ActionIn the docs only

Set a Status moves a conversation to another status in Pingmee, so the state your team sees matches what really happened elsewhere.

When to use it
a ticket closes in your helpdesk or a payment clears, and the matching chat should change state too.
Watch out
the available statuses come from Pingmee, not from Make; look at what the module offers instead of typing free text.
Pingmee10

Set an Answer Mode

ActionIn the docs only

Set an Answer Mode switches how a conversation is answered in Pingmee, which is handy when a chat must pass from one way of handling to another.

When to use it
a conversation needs a different kind of handling once another module has tagged it or changed its status.
Watch out
Make does not document the modes, so look at the choices the module shows and try each one with Run once.
Pingmee11

Update a Customer

ActionIn the docs only

Update a Customer rewrites the details of a person who already exists in Pingmee, so agents read current details rather than an old version.

When to use it
your CRM or shop records a change and Pingmee should follow it.
Watch out
the module needs to know which customer to change; map that value from an earlier step rather than guessing it.
Need help

Need help automating Pingmee with Make?

A person reads every message.

FAQ

Pingmee and Make: common questions

01Is the Pingmee Make integration free?
Yes, Pingmee is a standard app in Make, so you can use it on the Free plan. That plan has limits worth knowing: 2 active scenarios, 15 minutes at the shortest between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) remove the cap on active scenarios, allow a 1 minute interval and longer runs. Each module run on one bundle counts as one operation against your monthly credits.
02What do you need to connect Pingmee to Make?
A Pingmee account and a Make account are enough to start, since the documentation lists no other prerequisite. Add any Pingmee module, click Create a connection, optionally name it, then either authorize Make on the Pingmee page or paste the key Pingmee provides, and save. The connection is stored once and reused by every Pingmee module. Make has no dedicated connection guide for this app, so ask your Pingmee admin if the window requests a value you cannot locate.
03Does the Pingmee trigger in Make fire instantly?
No. Both Pingmee triggers, Watch New Conversation and Watch New Messages, are scheduled: Make checks Pingmee on the scenario's schedule and collects what arrived since the last check. A new scenario checks every 15 minutes by default. On the Free plan 15 minutes is also the shortest interval, while paid plans can check every minute. This type is inferred from the module names, because the Make directory gave no detail on Pingmee.
04What if a Pingmee module is missing in Make?
It depends on what you need, because Pingmee has no Make an API Call module in Make, so you cannot reach beyond the 13 modules listed. Make also warns that its documentation for this app is limited. If an action is missing, check whether another app in your stack can hold that step, or have someone who knows Make well review your scenario before you build around the gap. First, check your need against the 11 actions: tags, agents, customers, statuses, answer modes and templates.
05Should you use Make or n8n for Pingmee?
It depends on which editor your team already uses. Pingmee may also have an n8n node, and both tools let you build the same kind of flow: a trigger on conversations or messages, then actions on tags, agents and customers. In Make you get the 13 modules described here, a visual scenario editor and a Free plan to test with. Compare the node list on the n8n side before deciding, and pick the editor where the steps you need actually exist.
Same platform

Other docs you might need on this stack.

Browse all integrations