Resources · Make integration

Uspacy Make integrationAutomate Uspacy with Make.

Can Make fill your Uspacy CRM while you work in other tools? Yes: the Uspacy Make integration gives you 13 modules, 12 actions and 1 search. This guide is for sales and ops teams, and it walks you from the connection to a working first scenario.

Try the Uspacy integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Uspacy Make integration let you automate?

The Uspacy Make integration links your Uspacy account to Make so that other apps can write into your CRM for you. You build a scenario (the automation you assemble in Make, a chain of modules), and each module is one brick: here, mostly actions that create or update records in Uspacy, plus one search.

Leads that arrive already filed. When a prospect comes in through another tool, Create a Lead records it in Uspacy and Create a Task reminds a salesperson to call back. Nobody retypes a name.

A clean handover from marketing to sales. Search Entity checks whether the person is already in the CRM, then Update an Entity refreshes the record or Create a Contact adds a new one, and Create a Deal opens the opportunity.

Documents and notes in the right place. Upload a File sends an attachment to Uspacy and Create a Comment leaves the context your colleagues need.

Two limits to know. Uspacy has no trigger in Make, so a scenario starts from another app or from a schedule. And Make's own documentation for Uspacy is limited, because little public information exists about the app; when a listed module falls short, Make an API Call reaches the rest of the Uspacy API with the same connection. If you are weighing tools, the n8n vs Make comparison lays out the differences, and Make pricing explains what a plan includes. For a guided start, see Make training.

Connect

How do you connect Uspacy to Make?

  1. 01

    Add a Uspacy module

    In your scenario, click the + and search for Uspacy, then pick any of its modules, Create a Contact for instance. A panel opens with a Create a connection button: click it. A connection is your Uspacy account linked to Make once.

  2. 02

    Name the connection

    Make offers a name field. It is optional, but a clear name such as the workspace or team it belongs to helps later, when several people share the same Make organization and pick a connection from a list.

  3. 03

    Authorize Make and save

    Depending on what Uspacy asks, you either approve access on the Uspacy page that opens or paste the key Uspacy gives you. Then click Save. Every Uspacy module in your scenarios reuses this connection.

First scenario

Your first scenario with Uspacy in Make

GoalWhen a form is filled in another app, Make creates the contact in Uspacy and opens a deal for it.

  1. 01

    Start from another app

    Create a new scenario from the Scenarios page and click the +. Uspacy has no trigger, so pick the trigger of the app that collects your prospects, such as your form tool.

  2. 02

    Add Create a Contact

    Click the + to the right of that first module, search for Uspacy and choose Create a Contact. Click Create a connection if you have not linked your account yet.

  3. 03

    Map the form answers

    Fill the fields by mapping the data of the first module: drag what the form received into the Uspacy fields that Make lists once the connection exists. You never type a value by hand.

  4. 04

    Open the deal

    Add Create a Deal after the contact module. If Make shows a field to link a contact, map the one just created, so the opportunity points to the right person.

  5. 05

    Test with Run once

    Click Run once, submit a test form, then open each module to read the bundle it received (a bundle is one item passed along, here one prospect). Check the record in Uspacy.

  6. 06

    Schedule and switch on

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

Modules

What each Uspacy module does in Make

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

Uspacy1

Create a Comment

ActionIn the docs only

You get the context from another tool written straight into Uspacy, as a remark your colleagues read without switching apps.

When to use it
a support conversation ends elsewhere and the account owner should see its summary next to the customer in the CRM.
Watch out
the documentation does not say which records accept comments, so open the module after connecting and let Make show you what it can target before the first test.
Uspacy2

Create a Company

ActionIn the docs only

This one saves you from typing organizations by hand: each bundle that reaches it becomes a company record in Uspacy.

When to use it
a signed quote or a new B2B signup in another app should give the sales team a company file ready to work on.
Watch out
the module creates, it does not check, so run Search Entity first if the company may already exist, or you will end up with duplicates.
Uspacy3

Create a Contact

ActionIn the docs only

People who reach you through forms, events or your shop land in Uspacy as contacts, with the details mapped from the earlier module.

When to use it
for someone you already know is a real person to follow, as opposed to an unqualified prospect, which fits Create a Lead better.
Watch out
one bundle makes one contact; if the source sends a list, each item produces its own record and its own operation.
Uspacy4

Create a Deal

ActionIn the docs only

With this module, an opportunity opens in your Uspacy pipeline the moment another app signals interest, so no sale waits for someone to remember it.

When to use it
right after Create a Contact or Create a Company, to attach the deal to the record the scenario just created.
Watch out
the documentation lists no fields, so check whether the module offers a link to a record; if so, map it from the previous module, never a fixed value.
Uspacy5

Create a Entity

ActionIn the docs only

Where the dedicated modules stop, this one lets you add a record of another kind that your Uspacy account exposes to Make.

When to use it
the item you need to create is not a contact, a company, a deal, a lead or a task, and Make lists it among the entities once the connection exists.
Watch out
the documentation does not describe the entity types, so pick yours from the list Make shows and test with Run once before going live.
Uspacy6

Create a Group

ActionIn the docs only

You can set up a new group in Uspacy from a scenario instead of opening the app each time a team or project needs one.

When to use it
a new client or project is confirmed in your project tool and its people should share a space in Uspacy.
Watch out
Make's documentation gives no detail on what a group holds in Uspacy, so read the fields Make proposes and check the result in the app after your first test.
Uspacy7

Create a Lead

ActionIn the docs only

Every prospect captured outside the CRM becomes a lead in Uspacy, ready for your sales team to qualify.

When to use it
the source is a web form, an ad platform or a chat tool, and the person has not been qualified yet; once they are, a contact or a deal takes over.
Watch out
a form submitted twice creates two leads, so put Search Entity in front when repeat submissions are likely.
Uspacy8

Create a Smart Object

ActionIn the docs only

If your team has shaped Uspacy with smart objects, this module fills them from Make just like the standard records.

When to use it
the data you track, say a contract or an onboarding file, lives in a smart object your workspace defined rather than in a contact or a deal.
Watch out
the documentation does not explain smart objects, so select the object in the module and let Make list the fields it can fill.
Uspacy9

Create a Task

ActionIn the docs only

Follow-ups stop living in people's heads: the scenario puts a task in Uspacy for whoever needs to act next.

When to use it
after a new lead or deal is created, so a salesperson has the callback in their list without anyone assigning it by hand.
Watch out
place it after the module that creates the record; if the task can point to a record, map the one that same run produced.
Uspacy10

Make an API Call

ActionIn the docs only

Anything the other twelve modules cannot do, this one can reach, by calling any endpoint of the Uspacy API with the connection you already set up.

When to use it
you need an operation the list lacks, such as reading or deleting a record, and Uspacy's API offers it.
Watch out
you write the request yourself from Uspacy's API reference, since Make's documentation for the app is limited; test with Run once and read the response bundle.
Uspacy11

Search Entity

SearchIn the docs only

Before writing anything, this search tells you what Uspacy already holds, which keeps your CRM free of duplicates.

When to use it
in front of a create or update module, to decide whether a person or a company is new or already on file.
Watch out
a search can return zero, one or several bundles, and every module after it runs once per result, so add a filter when only one match should go on.
Uspacy12

Update an Entity

ActionIn the docs only

Records in Uspacy stay current without manual edits: this module changes an existing entry with fresh data from another app.

When to use it
a customer changes their phone number in your billing tool, or a deal moves forward elsewhere, and Uspacy should reflect it.
Watch out
it needs the record to change, so pair it with Search Entity and map the found item; an update overwrites the old value.
Uspacy13

Upload a File

ActionIn the docs only

Attachments collected elsewhere end up in Uspacy, next to the people and deals they concern, instead of scattered across inboxes.

When to use it
a signed contract arrives by email or a client sends a document through a form, and your team should find it in the CRM.
Watch out
on the Free plan Make handles files up to 5 MB, so a larger scan will fail there; map the file from the module that received it.
Need help

Need help automating Uspacy with Make?

A person reads every message.

FAQ

Uspacy and Make: frequent questions

01Is the Uspacy Make integration free?
Yes, Uspacy is a standard app in Make, so its modules are available on the Free plan. That plan has limits worth knowing: 2 active scenarios, at least 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 and Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in credits, one per operation, each month. Your Uspacy subscription is a separate matter.
02What do you need to connect Uspacy to Make?
A Uspacy account and a Make account are enough to begin, since Make's documentation lists no other prerequisite. Add any Uspacy module, click Create a connection, give it a name if you like, then either approve access on the Uspacy page or paste the key Uspacy provides, and save. That single connection is reused by all 13 modules. If the authorization is refused, check which Uspacy account you are signed in with and start the connection again from the module.
03Does the Uspacy Make integration react in real time?
It depends on the app that starts your scenario, because Uspacy has no trigger module in Make. Its 13 modules are actions and a search, so they run when something earlier in the scenario hands them a bundle. You can open the flow with an instant trigger from another app, which that app calls as soon as an event happens, or with a scheduled trigger that Make checks on the scenario's schedule, every 15 minutes by default. You can also run the scenario on its schedule alone.
04What if a Uspacy module is missing in Make?
Use Make an API Call. It calls any endpoint of the Uspacy API with the connection you already have, so an operation the other modules lack, such as reading or deleting a record, stays within reach. You will need Uspacy's own API reference to write the request, because Make states that its Uspacy documentation is limited for lack of public information about the app. Test each call with Run once and read the bundle it returns before switching the scenario on.
05Should you use Make or n8n for Uspacy?
Base the choice on your case rather than on a ranking. On the Make side, Uspacy offers 13 modules covering leads, contacts, companies, deals, tasks, files and custom records, plus Make an API Call for the rest, and it works on the Free plan. Apps often have an n8n node too, so check whether Uspacy does and whether it covers the records you need. Then compare the two on the modules each one offers for your records, not on reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations