Aimsio and Jira Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build project management workflows between Aimsio and Jira on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Aimsio and Jira

Detailed info you need to know about Aimsio and Jira integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Aimsio

    • Project Management
    • 2 triggers
    • 31 searches
    • 17 actions

    Manage job orders, field tickets, employees, timecards, invoices and billable items in Aimsio.[5]

  • Jira

    • Project Management
    • 2 triggers
    • 290 searches
    • 327 actions

    Connect Jira Cloud issues, projects, and users to your workflows.[6]

How to connect Aimsio to Jira

Set up your Aimsio and Jira integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Aimsio and Jira work in WEXTL?

WEXTL exposes actions and triggers for Aimsio and Jira that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Aimsio triggersJira actions

Aimsio modules

  • Create or Update Billable Items Imports a Billable Item List into Aimsio, adding new items and editing ones that already exist. Items carry a Billable Item Name, Billable Item Category and Billable Item Default Rate. Output tallies Number Of Entities Created.
  • Create or Update Companies Adds or edits companies in Aimsio. Give each one a Company Name, Company Email and Company Phone, and a Company Type Uname such as Vendor Company Type, all inside the Company List.
  • Create or Update Contacts Saves contacts into Aimsio from a Contact List. Describe each with Contact First Name, Contact Last Name, Contact Email and Contact Phone, and set Contact Company Name to attach it to a company. Failures are counted separately as Number Of Entities Edited With Errors.
  • Create or Update Employees Loads an Employee List, adding or editing staff. Each person can have an Employee First Name, Employee Last Name and Employee Trade Code. Employment Type and Employee Status Uname record how and whether they are employed.
  • Create or Update Equipment Writes an Asset List so that pieces of equipment are added or edited in Aimsio. Each asset takes an Asset Code, Asset Serial Number, Asset Model and an Asset Status Uname of Active, Inactive or Repair And Maintenance.
  • Create or Update Job Orders Submits jobs to Aimsio from a Job List. Each entry can set a Job Number, Job Name and Job Status, name its client with Job Client Code, and add work breakdown activities with WBS Activity Name.
  • Create or Update Locations Syncs locations with Aimsio from a Location List. Use Location Code, Location Name and Location Type Uname to describe each place.
  • Create or Update Non-recurring Billable Items Uploads an NRB List of one-off billable charges. Each can carry an NRB Name, NRB Rate, NRB Quantity and NRB Job Order Number, with NRB Vendor Code for the supplier and NRB Invoice Number once billed.
  • Create or Update Pricebooks Stores a Price Book List together with the Price Item List inside each book. Use Price Book Action to add or update a book, or to replace it, and give each priced item a Price Item Rate.
  • Create or Update Users Brings a User List into Aimsio. Each user takes a User Name, User First Name, User Last Name and User Email, plus User Role Names and User Areas. Turn on User Is Active to mark the account active.
  • Delete Form Data Deletes one submitted form from Aimsio. Add a Deletion Reason to record why it was removed.
  • Get a Billable Item Opens one billable item from Aimsio. The result includes Billable Item Code, Billable Item Name, Billable Item Type Name and its Billable Item Default Rate.
  • Get a Binary File Downloads a stored file from Aimsio by its Binary File ID and returns the content as File Data.
  • Get a Company Reads one company from Aimsio, including its Company Code, Company Address, Company Notes and Company Form Data.
  • Get a Contact Looks up one person in Aimsio. Output has the Contact First Name, Contact Last Name and Contact Position Name, plus the Contact Company Name.
  • Get a Current Timecard Reads a single open timecard, with Time Card Employee Regular Hours, Time Card Employee Over Time Hours and the Time Card Pay Type.
  • Get a Field Ticket Looks up a single field ticket recorded in Aimsio, for use in later steps.
  • Get a Form Data PDF Renders one submitted form as a PDF file, available afterwards as Form Data.
  • Get a Job Order Fetches one job order. Output covers Job Name, Job Status, Job Client Name and Job Start Date, and lists the Job Crew Records and Job Equipment Records for the job.
  • Get a Location Reads a single location from Aimsio, returning its Location Code, Location Name and Location Type Name.
  • Get a Non-recurring Billable Item Opens one one-off charge, showing NRB Name, NRB Rate, NRB Quantity, NRB Vendor Code and whether NRB Is Billable.
  • Get a Non-recurring Billable Item PDF Exports one non-recurring charge as a PDF, handed over as File Data.
  • Get a Pricebook Reads one price book. Output has the Price Book Name and Price Book Origin Reference, along with every entry of the Price Item List.
  • Get an Employee Returns one employee from Aimsio with their Employee Code, Employment Hire Date, Employee Address and Employee Payroll Type Name.
  • Get an Invoice Reads an invoice from Aimsio with Invoice Number, Invoice Date, Invoice Client Name, Invoice Status, Invoice Sub Total and Invoice Total.
  • Get Equipment Reads one equipment asset from Aimsio with its Asset Serial Number, Asset Model, Asset Location and Asset Activation Date.
  • Get Form Data Reads one submitted form with its Form Data Status and Form Data Created By Full Name. Output also lists the Form Data Field Data List of answers and the Form Data Form Type Uname.
  • List Billable Items Reads the billable items defined in Aimsio. Each record is tagged with its Dtype, GUID and Updated At. Set a Limit to fetch only part of the catalog.
  • List Companies Retrieves every company stored in Aimsio. A record is identified by its GUID. Use Limit to stop the fetch at a chosen number of records.
  • List Contacts Returns contacts from Aimsio. Narrow them to one company with Company GUID or Company Code, and trim the total with Limit. Each result comes with an ID.
  • List Current Timecards Pulls the current timecards from Aimsio, identified by GUID. Use Limit to read only the first few.
  • List Employees Gathers the employee roster from Aimsio, one record per person. Pass a smaller Limit to fetch fewer.
  • List Equipment Lists the equipment assets Aimsio tracks, labelled by Dtype and GUID. Restrict the count with Limit.
  • List Field Tickets Fetches field tickets recorded in Aimsio, each with a GUID and an Updated At timestamp. Use Limit to read a set number of tickets.
  • List Form Data Finds submitted forms in Aimsio. Use Form Type Uname to search one form type only, and Limit to stop at a fixed count. A GUID identifies each match.
  • List Invoices Reads invoices from Aimsio and returns an ID, Dtype and Updated At for every one. Adjust Limit to control how many are fetched.
  • List Job Orders Collects the job orders in Aimsio. Enter a Limit to keep the list short, and read the GUID from each entry.
  • List Locations Shows the locations configured in Aimsio, each keyed by a GUID. Use Limit to decide how many records you get.
  • List Non-recurring Billable Items Returns the one-off billable charges in Aimsio, with GUID and Updated At on each. Use Limit when the account holds many and you want only some.
  • List Payroll Periods Lists payroll periods with the Payroll Period Name, Payroll Period Amount and Payroll Period Pay Type Name of each. Use Status to see only periods in one processing state.
  • List Pricebooks Loads the price books stored in Aimsio, telling them apart by GUID and Updated At. Cut the result short with Limit.
  • List Timecards Retrieves timecards, each with its Time Card Employee Code, Time Card Record Date and hours. Use Payroll Period GUID to see only the cards of one payroll period, or set Limit for a fixed count.
  • Make an API Call Makes an authorized free-form request to the Aimsio REST API with your saved credential.
  • Reopen Form Data Sends a submitted form back to an open state again. Reopen Reason records why.
  • Restore Form Data Brings a deleted form submission back into Aimsio.
  • Update Form Data Writes custom field values into existing form data. Identify each form with Form Data GUID, then give every Custom Field Data Uname a Custom Field Data String Value or Custom Field Data Boolean Value.
  • Update Invoices Edits invoices in bulk. Use Invoice ID to target each invoice, then change its Invoice Number or Invoice Custom Status, or set custom field values with Custom Field Data List.
  • Update Payroll Period Status Moves payroll periods to a new status. Choose a Payroll Period GUID and a Payroll Period Status for each entry of the Payroll Period List. The result counts Number Of Entities Edited.
  • Watch Contacts Runs on a polling schedule and emits each contact it finds, with its ID. Use Limit to bound a single poll.
  • Watch Invoices At each scheduled check, reads the invoices Aimsio returns and emits each as a separate item with its Updated At. Set Limit to keep a single check small.

Jira modules

  • Add a Comment Writes a new comment on an issue, with Body as an Atlassian Document Format object. Add Visibility to limit who can read it, or Properties to store extra data. Output is the new comment, including Created.
  • Add a Field to a Screen Tab Places a field on one tab of a screen. Turn on Skip Field Association to avoid linking the field to the projects that use the screen.
  • Add a Field to the Default Screen Places a field onto the default screen so issues created or edited with that screen show it.
  • Add a Filter as a Favorite Adds a filter to your favorites, identified by Id. Add Expand to include more filter detail in the output.
  • Add a Gadget to a Dashboard Places a gadget on a dashboard. Identify the gadget type with Module Key or Uri, and use Title, Color and Position to set its look and placement. Turn on Ignore Uri And Module Key Validation to skip that check.
  • Add a Share Permission Shares a filter beyond its owner. Set Type for the kind of target, then give the matching Account Id, Group Id, Project Id or Project Role Id, with Rights for the access level.
  • Add a User to a Group Puts a person into a group, identified by Account ID. Prefer Group ID over Group name, since a group can be renamed. Output reports the group Name.
  • Add a Vote Casts your own vote for an issue as the signed-in user.
  • Add a Watcher Subscribes a person, identified by Account ID, to updates on an issue.
  • Add a Worklog Logs work against an issue, with Time Spent or Time Spent Seconds, a Started time and a Comment. To change the remaining estimate, set Adjust Estimate and then New Estimate or Reduce By. Turn on Notify Users to notify users.
  • Add Actors to a Project Role Adds users or groups as actors of a role in a project. Use User for an account ID, or Group or Group Id for a group. Output is the role with its Actors.
  • Add an Atlassian Team to a Plan Brings an Atlassian team into a plan with a Planning Style of Scrum or Kanban. Optionally set a Capacity, a Sprint Length or an Issue Source Id.
  • Add an Attachment Uploads a File to an issue, optionally saved under a different File name. Output covers the Filename, Size and Mime Type of the new attachment.
  • Add Default Actors to a Project Role Adds default actors to a project role. Use User for a person, or Group or Group Id for a group. Output includes the Actors.
  • Add Issue Security Level Members Adds members to a level inside an issue security scheme. Use Members to list who joins, each with a Type.
  • Add Issue Security Levels Adds levels to an issue security scheme. Use Levels to give each level a Name, a Description, Members and whether it Is Default.
  • Add Issue Types to a Context Makes a custom field context apply to additional issue types. Use Issue Type Ids to add them.
  • Add Issue Types to an Issue Type Scheme Appends further issue types to an existing issue type scheme. Use Issue Type Ids to say which.
  • Add Notifications to a Notification Scheme Hooks notifications up to events of one scheme. Use Notification Scheme Events to pair each Event with the Notifications to send, each with a Notification Type.
  • Analyse a Jira Expression Examines Expressions for errors before you run them. Use Check to select the kind of analysis and Context Variables to supply the types involved. The output is the Results.
  • Append Mappings to an Issue Type Screen Scheme Extends a scheme with extra pairings of issue types and screens. Use Issue Type Mappings to list the pairs.
  • Archive a Plan Moves an existing plan into the archive, away from active planning.
  • Archive a Project Archives a project, found by its ID or key.
  • Archive Issue(s) by Issue ID/key Archives a hand-picked set of issues. Use Issue IDs or keys to choose them. Output reports Errors and the Number Of Issues Updated.
  • Archive Issue(s) by JQL Starts archiving every issue that matches a Jql search, running in the background.
  • Assign a Custom Field Context to Projects Limits a custom field context to particular projects, chosen with Project Ids, so the field shows only for them.
  • Assign a Field Configuration Scheme to a Project Connects a project to a field configuration scheme. Add Field Configuration Scheme Id to attach a specific scheme to the Project Id.
  • Assign a Permission Scheme Applies a permission scheme to a project, so access there follows that scheme. Use Expand to include extra detail. Output includes the Permissions of the scheme.
  • Assign a Workflow Scheme to a Project Moves a project onto a workflow scheme. Add Workflow Scheme Id to point at a specific scheme for the Project Id.
  • Assign an Issue Sets the person responsible for an issue. Add Account ID to hand it to a particular user, and clear it to unassign.
  • Assign an Issue Type Scheme to a Project Gives a project a different issue type scheme, so it offers the issue types that scheme defines.
  • Assign an Issue Type Screen Scheme to a Project Links a project to an issue type screen scheme, which decides the screens shown for each issue type there.
  • Assign Issue Types to Field Configurations Links issue types to field configurations within a field configuration scheme, based on Mappings.
  • Associate a Security Scheme with a Project Applies an issue security scheme to a project, using Old To New Security Level Mappings to translate existing levels to new ones. Output is a task report covering Status, Progress and Elapsed Runtime.
  • Associate Projects with Field Schemes Connects projects to field schemes in a single request. Use Payload to supply the mapping between them. The Results report how each link went.
  • Bulk Create Issues Raises many issues in one request, each defined by an entry of Issue Updates. The output lists the created Issues along with any Errors.
  • Bulk Create Statuses Creates several statuses at once. Define each status through Statuses and choose where they apply with Scope. The output lists each Status Category and Id.
  • Bulk Create Workflows Creates several workflows with their Statuses, within a chosen Scope. Add Workflows for the definitions. Output lists the Workflows created.
  • Bulk Delete an Issue Property Deletes a property from many issues at once. Narrow it with Entity Ids, or with Current Value to touch only issues holding that value.
  • Bulk Delete Issues Starts a background task that deletes many issues. Turn on Send Bulk Notification to send the bulk change notification. Output is the Task Id.
  • Bulk Delete Statuses Deletes several statuses together, chosen by their Id values.
  • Bulk Delete Worklogs Deletes a batch of worklogs from one issue, listed through Ids. Use Adjust Estimate to decide what happens to the remaining estimate, or Override Editable Flag to delete when editing is locked.
  • Bulk Edit Dashboards Applies one change to many dashboards at once, using Entity Ids to pick them. Set the Action, then supplement it with Change Owner Details or Permission Details. The output reports any Entity Errors.
  • Bulk Edit Issues Applies the same field edits to a set of issues, running as a background task. Use Selected Actions for the field IDs being changed and Edited Fields Input for their new values.
  • Bulk Fetch Changelogs Fetches the change history of many issues in one call, with the Change Histories of each issue. Use Field Ids to restrict changes to certain fields and Next Page Token to continue a long result.
  • Bulk Fetch Issues Loads many issues together from a list of Issue IDs or keys. Trim the data with Fields, include stored Properties, or set Limit to cap the count.
  • Bulk Get Custom Field Configurations Fetches the configurations of many custom fields in one call. Filter with Project Key Or Id, Issue Type Id or Field Context Id. The result includes Values, Total and Is Last.
  • Bulk Get Groups Lists groups, optionally filtered by Group ID, Group Name, Access Type or Application Key. Every group arrives with a Group Id and Name.
  • Bulk Get Statuses Fetches several statuses at once, matched by Id, including each Scope and Status Category.
  • Bulk Get Statuses by Name Looks up several statuses in a single call from their Name values, optionally within one Project Id.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Aimsio and Jira integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Aimsio and Jira on WEXTL®

Claim your 3-day trial to build Aimsio with Jira integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Aimsio and Jira.

How do I connect Aimsio and Jira?

Connect your Aimsio and Jira accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Aimsio and Jira?

Example: when the "Watch Contacts" trigger in Aimsio fires, WEXTL can "Add a Comment" in Jira. Aimsio has 2 triggers (including Watch Contacts and Watch Invoices). Jira has 617 actions (including Add a Comment, Add a Field to a Screen Tab, and Add a Field to the Default Screen). Add filters and transforms between steps when you need them.[1]

Can Aimsio trigger actions in Jira, and Jira in Aimsio?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Aimsio and Jira?

No. Aimsio-to-Jira automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Aimsio integrate with Jira in real time?

Yes. Trigger-based automations start the moment Aimsio (or Jira) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Aimsio + Jira integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Aimsio with Jira?

You can build your Aimsio + Jira automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Aimsio and Jira integration.

  1. Aimsio and Jira integration source code, module specs and credentials implementation.
  2. Our Aimsio and Jira integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Aimsio and Jira, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Aimsio integration information
  6. Jira integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Aimsio and Jira integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Aimsio and Jira, or get started