Resources · Make integration

easiware Make integrationAutomate easiware with Make.

Can Make react to your easiware tickets without a line of code? Yes. The easiware Make integration offers 18 modules, including 3 instant triggers, 10 actions and 5 searches. This guide is for support teams: connect your account, then build a first ticket scenario.

Try the easiware integration on MakeSee the 18 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the easiware Make integration do for your support team?

The easiware Make integration links your customer support desk to the rest of your tools. In Make, you build a scenario, the automation itself, out of modules, the bricks that each do one job: easiware tells Make the moment a ticket or a contact appears, and other modules read, create or update records for you.

Every new ticket, pushed to the right people. Start from Ticket Created, add Get a Contact to learn who wrote in, then send that context to the chat or CRM app your team already watches. Nobody has to refresh the easiware inbox to spot an urgent request.

Contacts kept in step with your other tools. When a signup lands in a form app, Search Contacts checks whether that person already exists in easiware. If the search comes back empty, Create a Contact adds them; otherwise Update a Contact refreshes the record. The 123FormBuilder Make integration is one possible source.

A trail of what happens on each ticket. Ticket Event fires on every new event of a ticket, and Get a User tells you which agent was involved, so you can log activity wherever your managers read reports.

Know the limits before you start: the Make documentation for easiware is marked as limited, with no list of fields and no troubleshooting section, so you discover the fields inside the editor. When a listed module falls short, Make an API call reaches the rest of the easiware API through the same connection. If you are still weighing tools, the n8n vs Make comparison sets the criteria side by side, and the Make pricing page explains how operations are counted.

Connect

How do you connect easiware to Make?

  1. 01

    Add an easiware module

    Open a scenario, click the +, type easiware and pick any module, for example Get a Ticket. Then click Create a connection. A connection is your easiware account linked to Make once, and every easiware module reuses it afterwards.

  2. 02

    Name the connection and authorize

    Give the connection a clear name if you like, such as the name of your support workspace, which helps once several accounts exist. Then either approve access on the easiware page that opens, or paste the key easiware gives you, depending on what the window asks for.

  3. 03

    Save and check the lists

    Click Save. Back in the module, open a dropdown: once the connection works, Make can read your easiware data and offers what it finds instead of asking you to type raw identifiers from memory.

First scenario

Your first scenario: turn form requests into easiware tickets

GoalWhen a customer sends a request through a form app, Make finds that person in easiware and opens a ticket linked to their record.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the canvas. This first slot holds the module that starts everything, here the form app your customers already use.

  2. 02

    Start from your form app

    Pick the trigger of the form tool that collects support requests and connect it. Each submitted form reaches Make as one bundle, a single item passed from module to module.

  3. 03

    Add Search Contacts

    Click the + to the right, search for easiware, choose Search Contacts and click Create a connection. Map the email from the form so Make looks for the matching customer.

  4. 04

    Add Create a Ticket

    Add Create a Ticket after the search and fill the ticket fields Make lists with the answers from the form, and map the contact the search returned so the ticket lands on the right record.

  5. 05

    Test with Run once

    Click Run once, then submit a test form. Open the bubbles above each module to read the bundles it received and check the new ticket in easiware.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. Each module execution counts as one operation, the unit Make deducts from your plan.

Triggers

What starts an easiware scenario?

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

easiware1Contact Created

Contact Created

Instant trigger

In Make“New contact is created in easiware”

Contact Created starts your scenario as soon as a new person lands in easiware. You get the fresh contact as a bundle, ready to copy into a CRM, a mailing list or a spreadsheet your sales team keeps.

How it fires
instant, easiware calls Make through a webhook as soon as the contact exists, so there is no polling interval to set.
When to use it
when your support desk is often the first place a customer shows up and other teams need to know about them.
Watch out
contacts that existed before you switched the scenario on will not be sent; only new ones are.
easiware2Ticket Created

Ticket Created

Instant trigger

In Make“New ticket is created in easiware”

With Ticket Created, each request opened in easiware becomes a scenario run of its own. That is the trigger to reach for when a new ticket should alert someone, create a task elsewhere or be enriched with the customer record before anyone reads it.

How it fires
instant, easiware calls Make through a webhook as soon as the ticket is created.
When to use it
when an urgent request must reach a channel your agents actually watch, instead of waiting in the queue.
Watch out
it reacts only to creation. A ticket that changes later is covered by Ticket Event, not by this module, so pick the one that matches the moment you care about.
easiware3Ticket Event

Ticket Event

Instant trigger

In Make“New ticket event is created in easiware”

Ticket Event hands you every new event recorded on a ticket, which lets you follow its life after creation rather than only its first minute. The result is a running history you can store or react to, one bundle per event.

How it fires
instant, easiware calls Make through a webhook as soon as the event is created.
When to use it
when managers want an activity log outside easiware, or when a specific kind of event should notify another team.
Watch out
a busy ticket can produce many events, and each one runs the scenario, so add a filter early if you only care about some of them.
Modules

What else can Make do in easiware?

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

easiware1

Create a Contact

Action

In Make“Create a new contact in easiware”

Create a Contact adds a new person to easiware from data arriving in your scenario, so agents already see the customer when the first ticket lands.

When to use it
after a signup form or a purchase in another app, when that customer may contact support later.
Watch out
run Search Contacts first, otherwise the same person can end up recorded twice.
easiware2

Create a Ticket

Action

In Make“Create a new ticket in easiware”

Create a Ticket opens a request in easiware on behalf of a customer, which brings messages from outside channels into the queue your agents already work from.

When to use it
when a complaint arrives by form, chat or email in a tool easiware does not read directly.
Watch out
link the ticket to an existing contact where you can, so the history stays in one place.
easiware3

Get a Category

Action

In Make“Get a category by easiware internal identifier”

Get a Category returns the details of one easiware category from its internal identifier, turning a bare ID carried by a ticket into something a person can read.

When to use it
before posting a ticket summary to a channel, so the message shows the category name rather than a number.
Watch out
you need the exact identifier; if you only know part of the name, use Search Categories instead.
easiware4

Get a Contact

Action

In Make“Get a contact by easiware internal identifier”

Get a Contact fetches the full record of one customer when you already hold their easiware identifier, typically handed over by a trigger or a ticket.

When to use it
right after Ticket Created, to add the customer details the ticket alone does not carry.
Watch out
this module expects the internal identifier, not an email address; to find someone by other details, Search Contacts is the better fit.
easiware5

Get a Ticket

Action

In Make“Get a ticket by easiware internal identifier”

Get a Ticket reads one ticket in full from its easiware identifier, which is handy when a scenario only received a reference and needs the rest of the ticket.

When to use it
after Ticket Event, to know which request the new event belongs to.
Watch out
it reads a single ticket; to go through several, Search Tickets returns them as separate bundles.
easiware6

Get a Ticket Event

Action

In Make“Get a ticket event by easiware internal identifier”

Get a Ticket Event gives you the detail of one event on a ticket, found by its internal identifier, so a scenario can look closer at a single step in the ticket history.

When to use it
when another tool stored an event reference and you now need the full event to decide what to do.
Watch out
for events arriving live, the Ticket Event trigger already delivers them; this module is for looking one up afterwards.
easiware7

Get a User

Action

In Make“Get a user by easiware internal identifier”

Get a User tells you who an easiware user is, an admin or an agent, from their internal identifier. It turns a bare user ID into a name your team recognizes.

When to use it
when a notification or report should say which agent handles a ticket.
Watch out
it covers staff accounts, not customers; for the person who opened the ticket, go through Get a Contact.
easiware8

Make an API call

Action

In Make“Make a generic API call to easiware servers”

Make an API call lets you reach any endpoint of the easiware API from your scenario, reusing the connection you already created, for jobs no listed module covers.

When to use it
when you need something outside the 18 modules, such as an object easiware exposes through its API but Make does not list.
Watch out
the Make documentation for easiware is limited, so you will need the easiware API reference to know the path and the data to send.
easiware9

Update a Contact

Action

In Make“Update an existing contact in easiware”

Update a Contact changes an existing easiware contact, so the details your agents read match what another system holds.

When to use it
when a customer's details change in your CRM and support should see the new version without retyping it.
Watch out
you must know which contact to change, so place Search Contacts or a trigger before it to supply the identifier.
easiware10

Update a Ticket

Action

In Make“Update an existing ticket in easiware”

Update a Ticket edits a ticket that already exists, letting another tool move a request forward without an agent opening easiware.

When to use it
when an action elsewhere, such as a refund processed in your billing app, should be reflected on the matching ticket.
Watch out
if the ticket itself triggers the scenario, updating it could start another run, so check your filters before switching on.
easiware11

Search Categories

Search

In Make“Search for categories in easiware”

Search Categories lists easiware categories that match your criteria, which saves you from hunting for identifiers when a scenario must file tickets in the right place.

When to use it
before Create a Ticket, to pick the category that fits the incoming request.
Watch out
a search can return zero, one or several bundles, and each one runs the modules placed after it.
easiware12

Search Contacts

Search

In Make“Search for contacts in easiware”

Search Contacts finds customers already stored in easiware, which is the safest way to decide between creating a record and updating one.

When to use it
when data about a person arrives from a form or a shop and you want to know whether support already knows them.
Watch out
an empty result is a valid answer; plan what the scenario does when nobody matches, typically Create a Contact.
easiware13

Search Ticket Events

Search

In Make“Search for ticket events in easiware”

Search Ticket Events pulls a set of events from easiware in one go, useful for looking back at what happened on tickets rather than waiting for new events.

When to use it
when you build a report or an export of past ticket activity for a manager.
Watch out
every event returned becomes its own bundle and uses operations downstream, so narrow the search before sending results onward.
easiware14

Search Tickets

Search

In Make“Search for tickets in easiware”

Search Tickets returns the tickets that match what you look for, so a scenario can act on a whole group of requests instead of a single one.

When to use it
when a customer writes from another channel and you want to check whether they already have an open ticket before creating a new one.
Watch out
several matches mean several bundles; add an aggregator if the next app expects one message.
easiware15

Search Users

Search

In Make“Search for users (admins & agents) in easiware”

Search Users looks through the admins and agents of your easiware account, which helps when a scenario must assign or notify someone by name rather than by identifier.

When to use it
when a ticket should go to the agent who matches a rule set in another tool.
Watch out
it only returns staff accounts, never customers; those live under Search Contacts.
Need help

Need help automating easiware with Make?

A person reads every message.

FAQ

Questions people ask about easiware and Make

01Is the easiware Make integration free?
Yes, easiware is a standard app in Make, so you can use it from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, runs of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow runs of up to 40 minutes. Usage is counted in credits, one per operation. Your easiware subscription is a separate matter.
02What do you need to connect easiware to Make?
You need an easiware account and a Make account. The Make documentation for easiware lists no prerequisite and no dedicated connection steps, so the usual flow applies: add an easiware module, click Create a connection, give it a name if you want, authorize Make on the easiware page or paste the key easiware provides, then click Save. If the authorization screen asks for access you do not have, the person who administers your easiware account is the one to ask.
03Do easiware triggers in Make react in real time?
Yes. All 3 easiware triggers, Contact Created, Ticket Created and Ticket Event, are instant triggers. easiware calls Make through a webhook as soon as the contact, the ticket or the event is created, instead of Make checking on a schedule. You therefore do not wait for the default 15 minute interval that scheduled triggers use. Each call still starts a run, so a busy help desk means many runs, and every module in the scenario counts operations on your plan.
04What if the easiware module you need is missing in Make?
It depends on what is missing. easiware has a Make an API call module, which reaches any endpoint of the easiware API with the connection you already set up. That is the way to cover what the 18 listed modules do not. The catch is documentation: Make marks its easiware guide as limited, so you will need the easiware API reference to write the request. If that is out of reach, a specialist can help you design the call.
05Should you use Make or n8n with easiware?
It depends on your criteria rather than on a ranking. On Make, easiware comes with 18 modules, 3 instant triggers and a generic API call module, and it is available from the Free plan. The same app may also have an n8n node, so check both catalogs for the exact modules your scenario needs. Compare how each tool counts usage against your ticket volume, and which editor your team finds easier to maintain, then test a small scenario in each before deciding.
Same platform

Other docs you might need on this stack.

Browse all integrations