Resources · Make integration

User.com Make integrationAutomate User.com with Make.

Can Make keep User.com fed with what happens in your other tools? The User.com Make integration offers 52 modules, 35 actions and 17 searches, covering users, companies, deals, tickets and events. This guide takes marketing and ops teams from the connection to a first working scenario.

Try the User.com integration on MakeSee the 52 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the User.com Make integration let you automate?

The User.com Make integration lets a Make scenario, the automation you build as a chain of modules, read and write your User.com data. Each module is one brick: here, an action that creates or updates a record, or a search that finds users, deals or tickets. You link your account once, then drag the bricks you need.

Every sign-up lands in the right audience. A form or a shop order in another app hands its details to Update or Create a User, then Add a User to the List places the person where your campaigns look. No copy and paste, no duplicate when the same person comes back.

Sales sees deals where they already work. A demo request opens a deal with Create a Deal, a signed quote updates it with Update a Deal by Custom ID, and Add a Company Member ties the contact to its account.

Support never loses a request. A complaint received by email becomes a ticket through Create a Ticket, and Update a Ticket reflects the fix once your developers ship it.

One limit shapes every design: User.com has no trigger module in Make, so it cannot start a scenario by itself. The first module comes from another app, or the scenario runs on Make's schedule. Make also states that its User.com documentation is AI-generated from the vendor's docs, so check important details with User.com. If you are weighing tools, the n8n vs Make comparison lays out the criteria, and the Make training helps you build these flows yourself.

Connect

How do you connect User.com to Make?

  1. 01

    Create an API key in User.com

    In User.com, open Settings, then App Settings, Advanced and Public API. Click Create API key, give it your application name, set the key parameters you need and copy the key shown on screen.

  2. 02

    Open a User.com module in Make

    In your scenario, add any User.com module and click Create a connection. A connection is your User.com account linked to Make once, then reused by every User.com module. The Connection name field is optional but helps when you manage several accounts.

  3. 03

    Paste the key and save

    Paste the API key you copied into the connection window, or follow the on-screen instructions, and confirm. The module now lists what it can read in your account, and you are ready to fill its fields.

First scenario

Your first User.com scenario, step by step

GoalWhen a new lead reaches another app, Make writes it into User.com and adds it to a list.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the +. Since User.com has no trigger, pick the app where your leads arrive first, such as your form or shop tool.

  2. 02

    Add Update or Create a User

    Click the + to the right of that first module, search for User.com and choose Update or Create a User. Create the connection, then map the email and name coming from the previous module.

  3. 03

    Add the contact to a list

    Add Add a User to the List after it. Map the user returned by the step before and choose the list, which Make can show you now that the connection exists.

  4. 04

    Test with Run once

    Click Run once and send a test lead. Each module shows the bundles it received, a bundle being one item passed along, here one contact. Check the person appears in User.com and in the list.

  5. 05

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Every module run on a bundle counts as one operation on your Make plan.

Modules

What each User.com module does

User.com gives you 52 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

User.com1

Add a Company Member

Action

In Make“Adds an existing user to a specific company.”

Your contact now appears inside the right company account, so sales and support see at a glance who belongs where. The module links an existing user to a company; it does not create either one.

When to use it
a new sign-up uses a work email from a client company you already track.
Watch out
if the person may be missing, run Update or Create a User first and map its result here.
User.com2

Add a Company Tag

Action

In Make“Adds a tag to a specific company.”

A label lands on the company record, which lets you filter accounts and build segments in User.com without editing each one by hand. You target the company through its User.com record.

When to use it
a company signs its contract and should move into your customers view.
Watch out
tags pile up quickly; List All Tags shows what already exists before you create a near duplicate.
User.com3

Add a Company Tag by Custom ID

Action

In Make“Adds a tag to a specific company by custom company id.”

Same outcome as tagging a company, reached through the custom company ID instead of the User.com record. That saves a lookup when your own reference is what travels through the scenario.

When to use it
your invoicing tool passes its client code and the account should be flagged as paid.
Watch out
the custom ID in the scenario has to match the one saved on the User.com company, character for character.
User.com4

Add a Product Tag

Action

In Make“Adds a tag to a specific product.”

Products receive a tag you can reuse in segments and campaigns, so the catalog stays organized from the scenario rather than by hand. You point to the product through its User.com record.

When to use it
an item goes on promotion and should join the group your emails draw from.
Watch out
none of the listed modules removes a product tag, so decide early how the tag goes away when the promotion ends.
User.com5

Add a Product Tag by Custom ID

Action

In Make“Adds a tag to a specific product by custom product id.”

The product gets tagged through its custom product ID, which fits when your shop or inventory tool sends its own reference into the scenario. No search in User.com is needed first.

When to use it
stock hits zero in your inventory tool and the item should carry an out of stock tag.
Watch out
one bundle means one product and one operation, so tagging a whole batch runs this module once per item.
User.com6

Add a User to the List

Action

In Make“Adds a specific user to the list.”

The person joins a User.com list, ready for the campaigns and views built on it. It is the shortest path from an event in another tool to a place in your audience.

When to use it
a webinar registration arrives and the attendee should enter your follow-up list.
Watch out
the user has to exist already, so place Update or Create a User before this module.
User.com7

Add a User to the List by Custom ID

Action

In Make“Adds a specific user to a list by custom user id.”

Puts someone on a list using the custom user ID, handy when your product database, not User.com, decides who a person is. The scenario skips the lookup and goes straight to the list.

When to use it
your app flags an account as a trial and you want it in the trial nurture list.
Watch out
map the custom user ID from the previous module; a value typed by hand would add the same person on every run.
User.com8

Create a Company

Action

In Make“Creates a new company.”

A brand new company record appears in User.com, giving deals, members and tags a home. Choose it when you know for sure the account has never been tracked.

When to use it
a form where the visitor ticks a business option announces a company unknown to your team.
Watch out
this module always creates; if the same company can come in twice, Update or Create a Company keeps a single record.
User.com9

Create a Deal

Action

In Make“Creates a new deal.”

You get a new deal in User.com, opened straight from whatever signal told you a sale is starting, with nobody retyping the details.

When to use it
a demo request lands through your website and the sales team wants an opportunity waiting for them.
Watch out
a form submitted twice means two deals; when that risk exists, pick Update or Create a Deal instead.
User.com10

Create a Ticket

Action

In Make“Creates a Ticket.”

A support ticket opens in User.com without anyone copying the request by hand, so the issue joins the same queue as every other one.

When to use it
a complaint arrives by email or through a review tool and deserves the same follow-up as a chat request.
Watch out
each bundle creates one ticket; if a search sits before this module, make sure it returns one item, not a batch.
User.com11

Create a User

Action

In Make“Creates a new User.”

A fresh contact is created in User.com, ready for tags, lists, events and deals. It is the direct route when the person is certainly unknown.

When to use it
a paid order comes in from your shop with a first-time buyer's details.
Watch out
returning customers would be duplicated, which Update or Create a User avoids by handling both cases in one module.
User.com12

Find User by User Key

Action

In Make“Finds user based on the user_key attribute.”

Hands back the User.com contact whose user_key attribute matches the value you pass, so the next modules get the whole record instead of a bare identifier.

When to use it
an earlier step gives you a user_key and you need the person behind it before tagging or updating.
Watch out
Make files it as an action even though it finds someone, so plan what happens when the key matches nobody.
User.com13

Get a Company by Custom ID

Action

In Make“Returns a specific company by custom company id.”

Brings back one company's details from its custom company ID, so a scenario that only knows your internal reference can still read the full User.com record.

When to use it
an invoice from your accounting tool names a client by its code and you want the account's details before replying.
Watch out
it reads and changes nothing; pair it with an Update module when the goal is to edit.
User.com14

Get a Deal by Custom ID

Action

In Make“Returns a specific deal by custom deal id.”

The deal your own system knows by a custom ID comes back with its User.com details, ready to map into the next step of the scenario.

When to use it
your contract tool reports a signature with its deal reference and you want to check the deal before closing it.
Watch out
to change the deal afterwards, Update a Deal by Custom ID does it in one module, with no read needed first.
User.com15

Get a Single Company

Action

In Make“Returns a specific company details.”

Reads one company as User.com stores it, giving the following modules every detail of that account to map into messages or other apps.

When to use it
a ticket or a deal points to a company and the alert sent to your team should include its details.
Watch out
it targets the company's User.com record; with only your own reference, Get a Company by Custom ID is the right choice.
User.com16

Get a Single Deal

Action

In Make“Returns a specific deal details.”

Pulls the details of one deal, so the scenario can react to what the opportunity contains before sending anything.

When to use it
before posting a win in your team chat, you want the deal's details inside the message.
Watch out
this returns one deal you already point to; to scan several, List All Deals or List Deals by Tag fit better.
User.com17

Get a Single Email Campaign

Action

In Make“Returns information about a specific email campaign.”

Returns information on one email campaign, so its details can reach the place your team actually reads, such as a shared sheet or a reporting tool.

When to use it
a marketer wants a campaign's information copied into a report after a send.
Watch out
click Run once and read the bundle first, so you see what comes back before mapping anything.
User.com18

Get a Single Ticket

Action

In Make“Returns a ticket.”

Fetches one ticket so its content can travel on, to a chat alert, a report or another team that needs to step in.

When to use it
an urgent flag comes from your monitoring tool and the person on call needs the ticket's details in their message.
Watch out
reading does not change the ticket; Update a Ticket is the module that edits it.
User.com19

Get a Single User

Action

In Make“Returns a specific user details.”

One contact's full record comes back, giving later modules everything User.com holds on that person to map wherever you need it.

When to use it
a deal changes owner and the new rep should receive the customer's profile by email.
Watch out
it targets the User.com record; if all you hold is an email address, Find Users by Email is the entry point.
User.com20

Get a Single User by Custom ID

Action

In Make“Returns a specific user details by custom user id.”

Reads a contact through the custom user ID your product assigns, so the scenario never has to translate your IDs into User.com's.

When to use it
your back office reports an account event and support needs the matching User.com profile.
Watch out
a wrong mapping sends the scenario looking for nobody; test with Run once on a real ID before switching on.
User.com21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the User.com API through the connection you already set up, which covers what the 52 ready modules leave out.

When to use it
you need an operation no listed module offers, and User.com's API documentation describes it.
Watch out
here you write the request yourself, reading the vendor's API docs, a step the ready modules spare you.
User.com22

Send an Event

Action

In Make“Sends an event.”

Records an event on a user, so something the person did in another tool becomes part of their User.com profile and usable for targeting.

When to use it
a customer downloads a price list from your site and marketing wants to reach everyone who did.
Watch out
to change the contact itself, such as a name or an email, use Update a User rather than an event.
User.com23

Send an Event by Custom ID

Action

In Make“Sends an event by custom user id.”

The same event, addressed through the custom user ID, which suits product teams whose app knows people by its own identifiers.

When to use it
your app reports that someone finished onboarding and User.com should know it before the next campaign.
Watch out
every event sent is one operation, so send the actions that change what you do next, not every click.
User.com24

Send a Product Event

Action

In Make“Sends a product event.”

Attaches an event to a product rather than a person, so what happens to an item becomes visible from User.com.

When to use it
an item sells out or gets restocked in your inventory tool and the change should show on the product.
Watch out
pick Send an Event when the action belongs to a person; this module is for the product itself.
User.com25

Send Product Event by Custom ID

Action

In Make“Sends a product event by custom product id.”

Logs a product event using the custom product ID, so your shop's own product reference is enough to reach the right item in User.com.

When to use it
your store knows items only by its own codes and each order should log an event on the products sold.
Watch out
an order with several items yields several bundles, so the module runs, and counts an operation, once per item.
User.com26

Update a Company

Action

In Make“Updates an existing company.”

Edits an existing company in User.com, keeping the account in line with what your other tools know about it.

When to use it
a client changes its name or address in your billing tool and User.com should follow.
Watch out
it only works on companies already there; for an account that may be new, Update or Create a Company is safer.
User.com27

Update a Company by Custom ID

Action

In Make“Updates a specific company by custom company id.”

Changes a company addressed by its custom ID, letting an accounting or ERP tool update User.com with the reference it already holds.

When to use it
a contract renewal is recorded in your accounting tool and the company record should reflect it.
Watch out
try it with Run once on a single company before activation, since a wrong mapping would edit the wrong account each time.
User.com28

Update a Deal

Action

In Make“Updates an existing deal.”

Brings an existing deal up to date from the scenario, so the pipeline mirrors what happened in the tools your team really uses.

When to use it
a quote gets accepted in your e-signature tool and the deal in User.com should say so.
Watch out
it needs the deal's User.com record; if an earlier module only gives your own reference, Update a Deal by Custom ID skips that step.
User.com29

Update a Deal by Custom ID

Action

In Make“Updates a deal by custom deal id.”

Updates a deal found through its custom ID, one module instead of a lookup followed by an edit.

When to use it
your quoting tool numbers deals its own way and sends a change for one of them.
Watch out
when the deal might not exist yet in User.com, Update or Create a Deal covers both cases in a single module.
User.com30

Update a Ticket

Action

In Make“Updates an existing ticket.”

Changes a ticket already open in User.com, so progress made elsewhere shows up where support works every day.

When to use it
a developer closes the linked bug in your project tool and the customer's ticket should reflect the fix.
Watch out
the scenario must know which ticket to edit, so keep its reference from the step that created it or find it with a ticket search first.
User.com31

Update a User

Action

In Make“Updates an existing User.”

Rewrites what User.com holds on an existing contact, keeping profiles aligned with your billing, shop or product tools.

When to use it
a customer changes their details in your billing tool and marketing should use the new ones.
Watch out
the user must already exist; place it after Find Users by Email or Get a Single User, which hand over the record.
User.com32

Update a User by Custom ID

Action

In Make“Updates a specific user by custom user id.”

Updates the contact your product knows by its custom user ID, without any search beforehand.

When to use it
a user upgrades inside your app and User.com should show the new status for targeting.
Watch out
when several changes for one person arrive together, each bundle is a separate run and a separate operation.
User.com33

Update or Create a Company

Action

In Make“Updates a company if exists, creates a company otherwise.”

Gives you one record per account whatever happens: the company is updated if it exists and created if it does not.

When to use it
companies come from a form or an import where nobody can tell who is already tracked.
Watch out
test it with Run once on a known account and on a new one, then compare both results in User.com.
User.com34

Update or Create a Deal

Action

In Make“Updates a deal if exists, creates a deal otherwise.”

A deal is either refreshed or opened, so a repeated signal never splits one opportunity into two records.

When to use it
your quoting tool resends a document each time it changes and the deal should follow each version.
Watch out
when the deal belongs to a person, have that user in User.com first, for instance with Update or Create a User earlier in the scenario.
User.com35

Update or Create a User

Action

In Make“Updates a user if exists, creates a user otherwise.”

The safest way to write a contact: an existing user is updated, a new one is created, and this scenario adds no duplicate.

When to use it
as the first User.com step after a form, a purchase or a sign-up in another app.
Watch out
its output is the contact record, so map it straight into Add a User to the List or Send an Event instead of searching again.
User.com36

Find Most Recent Message

Search

In Make“Returns most recent message.”

Hands your scenario the latest message from User.com, so a summary or an alert can quote what was said last.

When to use it
before a renewal call, the rep should receive the last exchange with the client in their inbox.
Watch out
as a search it can return nothing, and then the next modules have no bundle to work on; check the result with Run once.
User.com37

Find Users by Email

Search

In Make“Finds users based on an email attribute.”

Returns every User.com contact holding a given email address, the natural bridge from tools that only know people by their inbox.

When to use it
a reply arrives by email, or a form sends an address, and you need the matching profile.
Watch out
it can return several users; each one is a bundle and every module after it runs once per user.
User.com38

Find Users by Phone Number

Search

In Make“Find users based on a phone number attribute.”

Finds contacts from a phone number, which suits call and text messaging tools where the number is all you have.

When to use it
a missed call is logged in your phone system and the salesperson should know who tried to reach them.
Watch out
a shared office line can match several people, so check the bundles with Run once before acting on all of them.
User.com39

Get a Single Event

Search

In Make“Returns a list of specific event occurences.”

Returns the occurrences of a chosen event, so a scenario can forward or count them instead of someone opening User.com.

When to use it
the product team wants every occurrence of a sign-up event copied to a sheet for analysis.
Watch out
despite Single in its name, it can return many bundles, one per occurrence, and each one costs operations further down.
User.com40

Get a Single Product Segment

Search

In Make“Returns all products assigned to a specific product segment.”

Returns all the products placed in a given product segment, ready to feed a catalog export, a price check or a campaign.

When to use it
a merchandiser wants the items of a seasonal segment pushed to the spreadsheet the buying team reads.
Watch out
a large segment means many bundles; run it once to see the volume before switching the scenario on.
User.com41

Get a Single User Segment

Search

In Make“Returns all users assigned to a specific segment.”

You get every user of one User.com segment, each handed to the next module as its own bundle. Your targeting rules stay in User.com; Make just works through the people inside.

When to use it
a segment already holds your trial users and the sales team wants them in a spreadsheet.
Watch out
every user becomes a bundle, so each module after it runs, and counts an operation, once per person.
User.com42

List All Companies

Search

In Make“Returns all companies.”

This search pulls the full list of companies from your User.com account into the scenario, so you can export, compare or enrich the whole base at once instead of looking them up one by one.

When to use it
a full sync of your accounts toward a spreadsheet or another CRM; when you only need one company, Get a Single Company is cheaper.
Watch out
a large base means many bundles, and every module after this one repeats for each company.
User.com43

List All Deals

Search

In Make“Returns all deals.”

Your whole deal pipeline lands in Make, one deal per bundle, ready to be filtered, summed or pushed into a reporting tool that your sales managers already read.

When to use it
a pipeline review needs every open and closed deal together; for one account manager, List Deals by User keeps the list shorter.
Watch out
if only some deals matter, add a filter in Make right after the module, so the next steps skip the rest.
User.com44

List All Email Campaigns

Search

In Make“Returns information about all email campaigns.”

Every email campaign of your User.com account comes back with its information, which gives you one place to archive campaigns or build a simple recap for the marketing team.

When to use it
someone asks for a full history of sends outside User.com; if you already know which campaign you need, Get a Single Email Campaign returns just that one.
Watch out
each campaign is a separate bundle, so plan the next modules around one campaign at a time.
User.com45

List All Tags

Search

In Make“Returns all tags.”

This module returns the tags defined in User.com, so you can see the exact labels your team uses before a scenario starts tagging or filtering by them.

When to use it
while you build the scenario, run it with Run once, the editor button that executes the scenario a single time, and copy the right tag name into modules such as List Users by Tag.
Watch out
a tag name typed with a typo elsewhere in the scenario matches nobody, which is why checking the list first pays off.
User.com46

List All Tickets

Search

In Make“Returns information about all tickets.”

Support tickets from User.com arrive in the scenario with their information, which lets you feed a support dashboard or hand the backlog to another help desk tool.

When to use it
a complete export of the ticket queue; when a customer message points to a single case, Get a Single Ticket is the more precise choice.
Watch out
one ticket equals one bundle, and the modules that follow run for every ticket in the list.
User.com47

List All Users

Search

In Make“Returns all users.”

You receive every user record stored in User.com, the widest search of the app, ideal for a full copy of your contacts into a warehouse sheet or a second tool.

When to use it
a first bulk migration or an audit of the base; for a known person, Find Users by Email or Get a Single User avoid pulling everyone.
Watch out
this is where operations add up fastest, since each person turns into a bundle for every module downstream.
User.com48

List Companies by Tag

Search

In Make“Returns all companies including a specific tag.”

Only the companies carrying a given tag come back, so a label set by your team in User.com becomes a ready-made target list inside Make.

When to use it
a tag marks a stage, for example accounts flagged for renewal, and you want those companies sent to a sales task tool.
Watch out
if no company has the tag, the search returns zero bundles and the rest of the scenario does nothing, which is normal.
User.com49

List Deals by Tag

Search

In Make“Returns all deals including a specific tag.”

Deals marked with one tag are returned, which turns a label like "priority" into a focused list without exporting the whole pipeline.

When to use it
your sales team already tags the deals that deserve a follow-up or a manager review, so List All Deals would bring too much.
Watch out
check the exact spelling with List All Tags first, since a tag that does not match returns an empty result.
User.com50

List Deals by User

Search

In Make“Returns deals assigned to a specific user.”

This search gives you the deals assigned to one user of your User.com account, so each owner can receive a summary of their own pipeline.

When to use it
an account manager wants a personal recap sent by email or chat rather than the full list that List All Deals would return.
Watch out
the module needs to know which user you mean, so find that person first with a module such as Find Users by Email and map the result.
User.com51

List Products by Tag

Search

In Make“Returns all products including a specific tag.”

Products tagged in User.com come back as separate bundles, a quick way to act on a family of products that your team has already labeled.

When to use it
a tag groups products for a campaign or a catalog update and they should go to another tool in one pass.
Watch out
only products are covered here; users, companies and deals each have their own "by Tag" search.
User.com52

List Users by Tag

Search

In Make“Returns all users including a specific tag.”

You get the users carrying one tag, so a label added by a form, a campaign or a sales rep becomes a list you can act on elsewhere.

When to use it
tagged people need to join another tool, such as a webinar list or a follow-up sheet, without exporting the whole base.
Watch out
if the same scenario later adds or removes that tag, test with Run once first so you know how many people will be touched.
Need help

Need help automating User.com with Make?

A person reads every message.

FAQ

User.com and Make: frequent questions

01Is the User.com Make integration free?
Yes, User.com is a standard app in Make, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes 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, Enterprise) lower the interval to 1 minute and lift the limit on active scenarios. Usage is counted in operations, one per module run on a bundle. You still need your own User.com subscription.
02What do you need to connect User.com to Make?
An active User.com account and a valid API key. In User.com, open Settings, App Settings, Advanced, then Public API, click Create API key, name it after your application, set its parameters and copy the key while it is displayed. In Make, add any User.com module, click Create a connection, optionally fill the Connection name field, and paste the key. That single connection then serves all User.com modules, so you never paste the key twice.
03Can User.com start a Make scenario in real time?
No. User.com has no trigger module in Make, neither scheduled nor instant, so it cannot launch a scenario by itself. Two ways around it. Start the scenario with a trigger from another app, a form or a shop for example, then chain the User.com modules. Or let Make run the scenario on its schedule, every 15 minutes by default, with a User.com search such as List All Users as the first module.
04What if the User.com module you need is missing in Make?
Use Make an API Call. With it, the scenario can reach any endpoint of the User.com API through the connection you already created, which covers what the 52 ready modules do not. You write the request yourself, following User.com's API documentation, so start with one simple call and test it with Run once. Also note that Make presents its User.com documentation as AI-generated from the vendor's docs, so verify important details with User.com before relying on them.
05Should you use Make or n8n for User.com?
It depends on which tool your team already runs and maintains. On Make, User.com comes with 52 modules, 35 actions and 17 searches, plus Make an API Call for the rest, and the editor lets you test each step with Run once. Many apps also have an n8n node, so check whether one exists for User.com and what it covers before choosing. Compare on the criteria that matter to you, such as the modules you need and how your team prefers to build.
Same platform

Other docs you might need on this stack.

Browse all integrations