Axosoft Zapier integrationAutomate Axosoft with Zapier.
The Axosoft Zapier integration gives you 7 triggers, 7 actions and 0 searches. Enough to turn a new project, release or customer into ready-made items and work logs, without retyping anything in your backlog or chasing developers for updates.
Verified Trustpilot reviews · AI, automation & growth agency
What the Axosoft Zapier integration actually does
It links your Axosoft account to Zapier so that something happening in your backlog (a project, an item, a release, a work log) starts an automation, and that automation writes back into Axosoft for you. No code, no export: you pick an event, you pick what follows.
Three results worth building first. A project that arrives already scaffolded: New Project starts the Zap and Create Item drops the first features or defects inside it, so the board is never empty on day one. A customer record that comes with its people: New Customer fires, and Create Contact attaches a named person to that company. Commit history that lands on the right ticket: Create SCM Post pushes commit data to the items you tagged, which keeps developers out of copy-paste duty.
Now the limits, because they shape what you can build. Every trigger here is a polling one, so nothing is instant: on the free plan, a new item can wait up to 15 minutes before Zapier sees it. There are no search steps either, which means a Zap cannot look up an existing Axosoft item by name; to update one with Update Item you need its Id carried in from an earlier step. And there is no delete action at all, so cleaning up stays a manual job.
If you want to weigh the same app on another tool, the Axosoft Make integration page covers the Make side, and our Make vs Zapier comparison lays out the criteria.
Zapier vocabulary in one minute
Seven words you will meet in the editor. Read them once and the rest of the page reads faster.
- Zap
- The automation you set up on Zapier: one event to start it, then one or more steps that run each time that event happens.
- Trigger
- The event that starts a Zap, such as a new project in Axosoft. Once the Zap is switched on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that creates or changes something in an app, like a new item in your backlog.
- Task
- What Zapier bills: one action that completes successfully. The number printed on your plan is a count of those.
- Polling vs instant
- Polling means Zapier checks the app on a timer for anything new. Instant means the app calls Zapier itself. All Axosoft triggers poll.
- Filter
- A step that lets the Zap carry on only when the incoming data meets your condition, and stops it quietly otherwise.
- Multi-step Zap
- Any Zap with more than one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What an Axosoft Zap really costs
Axosoft is not a premium app, so it works on the free plan. What you pay for is tasks, not checks.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap size2 steps: one trigger, one action
- Axosoft on the free planYes, it is not a premium app
- Trigger checksFree, never counted as tasks
The trigger never costs a task, and neither does Zapier checking Axosoft for new records, however often it does it. Each action that succeeds counts once: a Zap that creates two items per new project uses two tasks per project. An action that fails is not counted. The catch on the free plan is size: a Zap there is one trigger plus one action. Add a second Create Item or a filter and you are on a paid plan.
Connect Axosoft to Zapier in 3 steps
- 01
Open your Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your Axosoft account linked once, then reused by every Zap that touches Axosoft.
- 02
Find Axosoft and confirm
Type Axosoft in the search box, select it, then click Add connection. A new tab opens on the Axosoft side so you can sign in with the account the Zaps should act as.
- 03
Sign in and grant access
Log in to Axosoft and allow Zapier to reach the account. You need read or write access on any project or item you do not own and still want a Zap to read or change.
Your first Zap: scaffold every new project
GoalEach new Axosoft project gets a spec item and a QA item, created for you.
- 01
Build: pick the trigger
Create a Zap, choose Axosoft as the app and New Project as the event. Pick your connection. If you only care about one branch of your tree, set the parent project here.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent projects of your account, so you map the next steps on a real project instead of a guess.
- 03
Add the first Create Item
Add Create Item. Choose the item type, map Project from the trigger, and type a name such as "Write the spec". Item type, project and name are all required.
- 04
Add the second Create Item
Add another Create Item for the QA work, same project mapping, different type and name. This second action makes it a multi-step Zap, so it needs a paid plan.
- 05
Test each step, then Publish
Test both actions and open Axosoft to check the two items are there. Then click Publish. From now on, each new project costs two tasks.
The 7 Axosoft triggers
7 events start a Zap when something happens in Axosoft. Zapier checks for them at the interval your plan allows.
New Contact
Polling triggerIn Zapier“Triggers when a new contact is created.”
Starts your Zap each time someone adds a contact in Axosoft, that is a person attached to one of your customer companies. You get that person as the starting point for whatever follows.
New Customer
Polling triggerIn Zapier“Triggers when a new customer is created.”
Fires when a customer appears in Axosoft. In Axosoft a customer is a company, a group under which contacts sit, so this is the moment a new account enters your system.
New Email
Polling triggerIn Zapier“Triggers when a new email is created.”
Reacts to emails logged in Axosoft, the messages tied to your work. It lets an exchange with a client become the starting point of a Zap instead of sitting in a thread nobody reopens.
New Item
Polling triggerIn Zapier“Triggers when a new item is created.”
The trigger for your backlog itself: every new item, whether a feature, a defect or another type you defined, can kick off a Zap. You decide which item type to watch when you set it up.
New Project
Polling triggerIn Zapier“Triggers when a new project is created.”
Catches projects as they are created, either anywhere or only under a parent project you point to. It is the natural start for anything you repeat at the beginning of a piece of work.
New Release
Polling triggerIn Zapier“Triggers when a new release is created.”
Runs when a release is created in Axosoft, at the top level or below a parent release. A release is where you group what ships together, so this trigger marks the start of a delivery cycle.
New Work Log
Polling triggerIn Zapier“Triggers when a new work log is created.”
Picks up each new work log, the time entries your people record against their items. That makes the hours spent on a ticket available to the rest of your Zap as soon as Zapier sees them.
The 7 Axosoft actions
Axosoft gives you 7 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a new contact.”
Adds a person under an existing customer company, with first name, last name and email, all required alongside the customer.
Create Customer
ActionIn Zapier“Creates a new customer.”
Registers a company as a customer. Axosoft groups people by company, so this is the container your contacts will hang from. The company name is the one required field.
Create Item
ActionIn Zapier“Creates a new item.”
Adds a new item to your backlog. You choose its type (feature, defect or your own), the project it lives in, and its name, all three required.
Create Project
ActionIn Zapier“Creates a new project.”
Opens a new project in Axosoft from data the Zap already carries. Only the name is mandatory, which keeps it quick to set up.
Create SCM Post
ActionIn Zapier“Posts the SCM commit data to any of your tagged items.”
Sends commit data from your source control into Axosoft, onto the items you tagged. It needs that message and your SCM API Key.
Create Work Log
ActionIn Zapier“Creates a new work log.”
Records time spent against work in Axosoft. You give the amount, the user who did it, the date and the time unit to save in.
Update Item
ActionIn Zapier“Updates an item.”
Changes an existing item. It needs the item's Id, plus the type, project and name, which are required here too.
When an Axosoft Zap breaks
Zapier lists no help article for Axosoft, so these are the general limits that hit this app hardest.
Two facts shape the risks here: every trigger polls, and several actions write into the very places those triggers watch. Read these four cases before you publish. When something still goes wrong, our Zapier troubleshooting page is the next stop.
Old records are never picked up
A Zap only reacts to what happens after you publish it. Projects, items or customers created before that stay out of reach; moving that backlog is a separate job.New Item plus Create Item loops
If a Zap watching New Item also runs Create Item for the same item type, each item it creates starts the Zap again, and your task count drains fast.A bulk import gets held back
After a migration or a mass import, a trigger can suddenly return a huge batch. Zapier's flood protection may hold it back instead of running every item.Required fields with no value
Create Work Log needs a user, a date, a unit and a conversion value. If an earlier step leaves one empty, the action fails and the record never appears.
Need help automating Axosoft with Zapier?
A person reads every message.
