Resources · Make integration

Axosoft Make integrationAutomate Axosoft with Make.

Can Make keep your Axosoft tickets, work items and customers moving without copy and paste? The Axosoft Make integration offers 36 modules, including 8 triggers. This guide connects your account and walks you through a first working scenario.

Try the Axosoft integration on MakeSee the 36 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Axosoft Make integration do for you?

The Axosoft Make integration links your Axosoft account to Make so that tickets, work items, work logs, contacts and customers can move between Axosoft and your other tools on their own. In Make you build a scenario, which is the automation itself: a chain of modules, where each module is one brick such as a trigger, an action or a search.

Support tickets that turn into planned work. Watch Tickets spots new tickets, and Create a Work Item adds the matching item to the backlog, so a bug reported by a customer lands where developers actually plan. Each item that flows between modules is called a bundle: here, one ticket.

Time tracking that reaches the rest of the company. Watch Work Logs picks up the hours your team records, and the next module can push them into a spreadsheet or a billing tool. Get a Work Item adds the context of the task the hours belong to.

One clean customer list. Watch Customers and Watch Contacts feed a CRM, while Search Customers checks whether a company already exists before Create a Customer adds it, which keeps duplicates out.

Know the limits before you start. All 8 Axosoft triggers are scheduled: Make polls Axosoft on the scenario's schedule rather than being called by the app, so nothing happens the instant a record changes. The official documentation is itself marked as AI-generated and may contain mistakes, so test each module with your own data. When a listed module does not cover your need, Make an API Call reaches the rest of the Axosoft API with the same connection.

Comparing tools first? The n8n vs Make comparison sets out the criteria, the Make pricing page explains plans and operations, and Make training helps if this is your first scenario.

Connect

How do you connect Axosoft to Make?

  1. 01

    Add an Axosoft module

    Log in to Make, open a scenario and add any Axosoft module. Click Create a connection. A connection is your Axosoft account linked to Make once, then reused by every Axosoft module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps as soon as you manage more than one Axosoft account, for example one for the support workspace and one for a client project.

  3. 03

    Enter your Axosoft credentials

    Paste the credentials you copied from your Axosoft account, or follow the instructions on screen to finish. You need an active Axosoft account; for custom OAuth2 credentials, create an application under Developer Applications in Axosoft and copy its Client ID and Client secret.

First scenario

Your first scenario with Axosoft and Make

GoalWhen a new ticket appears in Axosoft, Make creates a matching work item so the request reaches the development backlog.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario, then click the large + in the middle of the editor to add the first module.

  2. 02

    Add the Watch Tickets trigger

    Search for Axosoft, pick Watch Tickets and click Create a connection to link your account. Once connected, Make lists what it can read in Axosoft, so you choose from menus instead of typing.

  3. 03

    Add Create a Work Item

    Click the + on the right of the trigger, choose Axosoft again, then Create a Work Item. Fill its fields by mapping the data of the ticket bundle from the previous module.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received. Check that the new work item appears in Axosoft.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. Each check of Watch Tickets and each work item created counts as an operation on your plan.

Triggers

What can start an Axosoft scenario?

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

Axosoft1Watch Contacts

Watch Contacts

triggerIn the docs only

Contacts saved in Axosoft become the starting point of your scenario, one bundle per person, ready to be copied into a CRM or a mailing tool.

How it fires
scheduled. Make checks Axosoft on the scenario's schedule, every 15 minutes by default, and hands over the contacts it finds at each check.
When to use it
your support team adds the people behind each account in Axosoft and sales wants the same names in its own tool without typing them twice.
Watch out
each contact returned runs every following module once, and each run is an operation, so add a filter early if only some contacts matter.
Axosoft2Watch Customers

Watch Customers

triggerIn the docs only

Here the scenario starts from companies rather than people: every customer record Axosoft returns arrives as a bundle you can pass to accounting, a CRM or a welcome sequence.

How it fires
scheduled. Make asks Axosoft for customers on the scenario's schedule, so a new account appears at the next check, not the second it is created.
When to use it
a new client is signed, someone registers the company in Axosoft, and finance needs the same account opened in its own system.
Watch out
pair it with Watch Contacts only if you really need both levels, otherwise the same client triggers two parallel flows.
Axosoft3Watch Emails

Watch Emails

triggerIn the docs only

With this trigger, the emails Axosoft makes available to Make start the scenario one by one, which lets you archive them, forward a copy or log them elsewhere.

How it fires
scheduled. Make collects the emails on the scenario's schedule, with the Free plan allowing no less than 15 minutes between two runs.
When to use it
customer conversations tied to tickets must also be visible to a manager who never opens Axosoft.
Watch out
the documentation gives no detail on which emails are returned, so run it once and read the bundles before building anything on top.
Axosoft4Watch Projects

Watch Projects

triggerIn the docs only

Projects are the containers your team plans in, and this trigger hands each one it finds to the next module so the rest of your stack learns about it.

How it fires
scheduled. Make polls Axosoft for projects according to the schedule set on this first module, every 15 minutes unless you change it.
When to use it
a new client engagement opens as a project, and you want a shared folder, a chat channel or a line in a tracking sheet to follow automatically.
Watch out
new projects are rare compared with tickets, so a tight schedule mostly spends operations on empty checks; a wider interval is usually enough.
Axosoft5Watch Releases

Watch Releases

triggerIn the docs only

Releases mark what your team ships, and this trigger turns each one into a bundle that can announce the version, update a changelog or alert the people who waited for it.

How it fires
scheduled. Make looks for releases on the scenario's schedule, so the announcement leaves at the next check after the release is recorded.
When to use it
product and support both need to know when a version exists in Axosoft, without someone copying the notes by hand.
Watch out
test with Run once on a real release first, since the details a release carries into the bundle are not documented.
Axosoft6Watch Tickets

Watch Tickets

triggerIn the docs only

Incoming support requests are usually the most useful starting point: each ticket Axosoft returns becomes a bundle you can route, copy into the backlog or answer elsewhere.

How it fires
scheduled. Make checks Axosoft for tickets on the scenario's schedule, every 15 minutes by default, and faster only on a paid plan.
When to use it
a customer reports a bug, and you want it to reach developers as a work item or to ping the right channel without anyone watching the queue.
Watch out
this trigger is not instant and Axosoft does not call Make, so an urgent ticket still waits for the next check.
Axosoft7Watch Work Items

Watch Work Items

triggerIn the docs only

Work items are the tasks, bugs and features your developers plan, and this trigger passes each one it finds to the rest of the scenario.

How it fires
scheduled. Make polls Axosoft on the scenario's schedule; the clock badge on the module is there to remind you of that.
When to use it
planning happens in Axosoft, but a client or a manager follows progress in a sheet or a project board that should stay in sync.
Watch out
a scenario that watches work items and also creates or updates them can feed itself, so filter what comes back before the action module.
Axosoft8Watch Work Logs

Watch Work Logs

triggerIn the docs only

Hours your team records in Axosoft can leave the tool on their own with this trigger, one work log per bundle, for billing, payroll or reporting.

How it fires
scheduled. Make gathers work logs on the scenario's schedule, which by default runs every 15 minutes once the scenario is on.
When to use it
you invoice clients on time spent, and each logged entry should reach the billing spreadsheet with the client attached.
Watch out
a work log alone carries little context; add Get a Work Item after it when the next tool needs to know which task the hours belong to.
Modules

What can Make do in Axosoft?

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

Axosoft1

Create a Contact

ActionIn the docs only

Adds a person to Axosoft from data collected elsewhere, so the contact exists before your team needs to reach them about a ticket.

When to use it
a web form or a CRM captures a new client contact who should be reachable from the support side.
Watch out
run Search Contacts first, otherwise every repeat submission creates another copy of the same person.
Axosoft2

Create a Customer

ActionIn the docs only

Opens a new customer account in Axosoft, giving tickets and contacts a company to attach to from day one of the relationship.

When to use it
a deal is marked as won in your sales tool and the client must exist in Axosoft before support starts.
Watch out
pair it with Search Customers so a returning client does not end up with two accounts split across their history.
Axosoft3

Create a Ticket

ActionIn the docs only

Records a support request in Axosoft from any source Make can read, so no message stays stuck in an inbox or a chat thread.

When to use it
requests arrive through a form, a helpdesk mailbox or a chat tool and should all land in one Axosoft queue.
Watch out
map enough context from the source bundle; a ticket with only a title forces the agent back to the original message.
Axosoft4

Create a Work Item

ActionIn the docs only

Puts a new task, bug or feature into the Axosoft backlog, which is how requests coming from outside reach the people who plan development.

When to use it
a qualified ticket, a form answer or a line in a spreadsheet should become planned work without being retyped.
Watch out
if this runs after Watch Work Items in the same scenario, the item you create can be picked up again at the next check.
Axosoft5

Create a Work Log

ActionIn the docs only

Writes time spent into Axosoft from another tool, so hours tracked in a timer app or a calendar still count against the right item.

When to use it
your team tracks time outside Axosoft but reporting and billing are done from the Axosoft figures.
Watch out
hours are only useful on the right task, so find that item first with Search Work Items and map it from the result.
Axosoft6

Delete a Contact

ActionIn the docs only

Removes a contact from Axosoft, which keeps the address book aligned when someone leaves a client company or asks to be erased.

When to use it
a deletion request is confirmed in your CRM and the same person must disappear from Axosoft too.
Watch out
a deletion cannot be undone from Make, so add a filter that checks the exact contact before this module runs.
Axosoft7

Delete a Customer

ActionIn the docs only

Erases a customer account in Axosoft, useful for cleaning up test records or accounts that were opened by mistake.

When to use it
a duplicate company was found and merged elsewhere, and the extra record should go.
Watch out
the effect on contacts or tickets tied to the customer is not documented, so try it on a test account before any real data.
Axosoft8

Delete a Project

ActionIn the docs only

Takes a project out of Axosoft entirely, which is the most sweeping delete in this app and the one to handle with the most care.

When to use it
a cancelled engagement or a sandbox project should vanish once its closure is confirmed in another system.
Watch out
there is no undo from Make; keep a human approval step or a strict filter before this module in any scenario.
Axosoft9

Delete a Ticket

ActionIn the docs only

Deletes a ticket from Axosoft, handy for spam or duplicate requests that should not clutter the support queue.

When to use it
an upstream spam check flags a request that Create a Ticket already recorded.
Watch out
the deleted ticket is gone for good, so prefer Update a Ticket when you only want to close or reclassify it.
Axosoft10

Delete a Work Item

ActionIn the docs only

Pulls a work item out of the backlog when it should never have been there, so the plan stays readable for the developers.

When to use it
an automation created items from a source that turned out to be wrong, and you need to remove that batch.
Watch out
combine it with Search Work Items and check the result count with Run once before letting it delete for real.
Axosoft11

Delete a Work Log

ActionIn the docs only

Removes a time entry from Axosoft, which corrects reports and invoices when hours were logged twice or on the wrong item.

When to use it
a timer tool sent the same entry again, and the extra work log would inflate the client bill.
Watch out
once deleted, the hours are lost; if the entry is only misplaced, Update a Work Log is the safer choice.
Axosoft12

Get a Contact

ActionIn the docs only

Fetches the full record of one contact you have already identified, so the next module works with complete data rather than a bare reference.

When to use it
a previous module gave you the contact, and an email or a CRM update needs the rest of the details.
Watch out
it targets a single known contact; to find someone from partial information, start with Search Contacts.
Axosoft13

Get a Customer

ActionIn the docs only

Reads one customer account in detail, which adds company context to a ticket, a work log or a message before it leaves Axosoft.

When to use it
an invoice or a report built from work logs must show the client's account information.
Watch out
each call is an operation; when many bundles share the same customer, fetching it once per bundle adds up quickly.
Axosoft14

Get a Project

ActionIn the docs only

Returns the details of a single project, useful when a work item or a release points to it and the next tool needs its name and context.

When to use it
a status message about a release should name the project it belongs to in plain words.
Watch out
there is no Create or Update module for projects here, so this module reads only; changes go through Make an API Call.
Axosoft15

Get a Ticket

ActionIn the docs only

Pulls the latest state of one ticket, which matters when a scenario must decide what to do based on where that ticket stands now.

When to use it
before notifying a customer, you want the current version of their ticket rather than the copy caught by the trigger.
Watch out
it needs a ticket already known to the scenario; there is no Search Tickets module, so plan how you get that reference.
Axosoft16

Get a Work Item

ActionIn the docs only

Brings back one work item with its details, the natural companion of work logs and tickets that only point to the task.

When to use it
Watch Work Logs caught new hours, and the billing sheet should say which feature or bug they were spent on.
Watch out
placed after a trigger that returns many bundles, it runs once for each of them and every run is an operation.
Axosoft17

Get a Work Log

ActionIn the docs only

Reads a single time entry in full, which lets a scenario check the hours before passing them to payroll or an invoice.

When to use it
an approval flow needs the recorded entry exactly as Axosoft stores it before anyone signs off.
Watch out
to list several entries at once, Search Work Logs is the right module; this one returns only the log you point to.
Axosoft18

Make an API Call

ActionIn the docs only

Calls any endpoint of the Axosoft API with the connection you already set up, covering what the listed modules leave out.

When to use it
you need to create or change a project, or reach an Axosoft object that has no dedicated module in this list.
Watch out
you write the request yourself from the Axosoft API reference, so test it with Run once and read the response before going further.
Axosoft19

Search Contacts

SearchIn the docs only

Looks through Axosoft contacts and returns zero, one or several matches, each as its own bundle for the modules that follow.

When to use it
a form arrives with a person's details and you want to know whether they already exist before creating anyone.
Watch out
several matches mean the next module runs several times; add a filter or keep only the first result when one is enough.
Axosoft20

Search Customers

SearchIn the docs only

Finds customer accounts in Axosoft, the step that prevents duplicate companies when data comes from sales or billing tools.

When to use it
just before Create a Customer, to decide between opening a new account and updating an existing one.
Watch out
when no customer matches, no bundle comes out and the modules after it do not run; test both cases with Run once.
Axosoft21

Search Projects

SearchIn the docs only

Lists the projects that match what you look for, which is how a scenario picks the right place for a new work item or ticket.

When to use it
incoming requests name a client or product, and you want to file them under the matching project automatically.
Watch out
when two projects look alike, the scenario can receive both; check the bundles with Run once before mapping.
Axosoft22

Search Work Items

SearchIn the docs only

Retrieves the work items that fit your criteria, one bundle each, to report on them or to act on a whole group at once.

When to use it
a release is close and you want every related item sent to a status page or a stakeholder summary.
Watch out
a broad search can return many bundles, and each one multiplies the operations of the modules that come after.
Axosoft23

Search Work Logs

SearchIn the docs only

Gathers the time entries that match a search, which is the base for any report of hours by client, project or person.

When to use it
a client invoice needs every work log for one customer in a single spreadsheet.
Watch out
each entry comes out as a separate bundle; add an aggregator from Make if the next tool expects a single total.
Axosoft24

Update a Contact

ActionIn the docs only

Changes an existing contact in Axosoft so the person's details stay correct without anyone editing them by hand.

When to use it
a contact changes job or email in your CRM, and support should see the new information too.
Watch out
you need the right contact first, usually from Search Contacts; updating the wrong match overwrites someone else's record.
Axosoft25

Update a Customer

ActionIn the docs only

Edits a customer account in Axosoft, keeping company details aligned with the tool where they are really maintained.

When to use it
finance updates a client's billing details and Axosoft should reflect them for the support team.
Watch out
if both tools can edit the same account, decide which one wins, or two scenarios will keep overwriting each other.
Axosoft26

Update a Ticket

ActionIn the docs only

Moves a ticket forward in Axosoft from outside events, such as a fix shipped or an answer sent from another tool.

When to use it
a linked work item is done and the ticket that started it should reflect that for the customer.
Watch out
updating tickets inside a scenario that also watches tickets can loop; filter out the changes your own scenario made.
Axosoft27

Update a Work Item

ActionIn the docs only

Edits a work item already in the backlog, so status or details change in Axosoft when the work progresses in another tool.

When to use it
a pull request is merged or a client approves a feature, and the matching item should move without a manual click.
Watch out
map only the fields you mean to change and test with Run once, since an empty mapping can overwrite useful data.
Axosoft28

Update a Work Log

ActionIn the docs only

Corrects an existing time entry, which keeps hours accurate when a timer tool edits an entry after it was first sent.

When to use it
someone fixes their hours in the time tracker and Axosoft should carry the corrected value for billing.
Watch out
find the right log with Search Work Logs first; guessing the entry from the date alone risks editing a colleague's hours.
Need help

Need help automating Axosoft with Make?

A person reads every message.

FAQ

Axosoft and Make: common questions

01Is the Axosoft Make integration free?
Yes, on the Make side. Axosoft is a standard app, so its modules work on 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 and Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and count usage in operations per month. You still need your own active Axosoft account, whose subscription is billed by Axosoft and is not covered here.
02What do you need to connect Axosoft to Make?
An active Axosoft account and a Make account. In the scenario, add any Axosoft module, click Create a connection, give it a name if you like, then enter the credentials from your Axosoft account or follow the steps on screen. For your own OAuth2 credentials, create an application in the Developer Applications section of Axosoft, set the callback URI given by the Make documentation, then copy the Client ID and Client secret into Make. The connection is then reused by every Axosoft module.
03Do the Axosoft triggers in Make fire in real time?
No. The 8 Axosoft triggers are scheduled: Make asks Axosoft for new records on the scenario's schedule, and Axosoft does not call Make through a webhook. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans go down to 1 minute. For most ticket, work item or time tracking flows this delay is fine. If a case truly cannot wait, shorten the schedule on a paid plan and keep in mind that each check uses operations.
04What if an Axosoft module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Axosoft API with the same connection as the listed modules, which covers, for example, creating or editing a project, since the list only offers to get, search and delete projects. You write the request from the Axosoft API reference and test it with Run once. Keep in mind that the Make documentation for Axosoft is flagged as AI-generated and may contain mistakes, so check any important behavior against Axosoft's own documentation or its support.
05Should you use Make or n8n for Axosoft?
It depends on your criteria, not on a winner. On Make, Axosoft brings 36 modules, 8 scheduled triggers, a guided connection and Make an API Call for the rest, and it runs on the Free plan. Many apps also have an n8n node, so check whether one exists for Axosoft and what it covers before choosing. Compare the modules you actually need, how each tool counts usage and which editor your team already knows. The comparison page linked in this guide lists the criteria side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations