Ascora is a cloud-based field service management software designed to streamline operations for service-based businesses, offering features such as job scheduling, invoicing, customer management, and mobile access.
Ascora is a cloud-based field service management software designed to streamline operations for service-based businesses, offering features such as job scheduling, invoicing, customer management, and mobile access. On Nagent, Ascora is exposed as a fully-configurable crm integration that any agent can call — 23 actions, and API key authentication. No code is required to wire Ascora into your workflow — connect it once via the External Integrations panel and reuse it across every agent you build.
Agent builders use Ascora to automate the kinds of tasks crm teams previously handled manually. Concrete examples — each one is a single agent step in Nagent — include:
Every action and trigger is paired with a structured input/output schema (visible in the sections below), so when you wire Ascora into Helix — our agentic agent builder — the editor knows exactly what each step expects and produces. Configure once, deploy anywhere across your Nagent agents.
Every operation an agent can call against Ascora, with input parameters and output schema. Drop these into any step of an agent built in Helix.
ASCORA_CREATE_NOTECreates a note on an entity (customer, job, quote, etc.) in Ascora. Use this when you need to add comments, updates, or documentation to any entity in the system. Requires a valid entity ID from the Ascora system.
Input parameters
The text content of the note to be created. Can contain any text describing information, updates, or observations about the entity.
The unique identifier (UUID/GUID format) of the entity to attach the note to. Must be a valid UUID from the Ascora system.
The type of entity to attach the note to. Must be one of: Customer, Job, Quote, Enquiry, Invoice, PurchaseOrder, or Asset.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_CREATE_OR_UPDATE_CONTACTTool to create a new contact or update an existing contact for a customer. Use when you need to add or modify contact information for a specific customer in Ascora. Requires a valid customer ID and accepts optional contact details like name, email, phone numbers, and default contact flag.
Input parameters
The email address of the contact
The phone number of the contact
The last name of the contact
The fax number of the contact
The first name of the contact
The unique identifier of the customer to associate the contact with (UUID format)
The mobile number of the contact
Whether this is the default contact for the customer
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_CREATE_OR_UPDATE_CUSTOMERTool to create a new customer or update an existing customer in Ascora. Use when you need to add a new customer with company name and optional contact details, address information (street and postal), and communication preferences. If the customer already exists, their details will be updated.
Input parameters
Company name for the customer (required)
Phone number of the customer
Postal address line 1
Postal address line 2
Postal state
Street address line 1
Street address line 2 (e.g., unit or suite number)
Customer display name (defaults to CompanyName if not provided)
Email address of the customer
Mobile number of the customer
Postal suburb
Street suburb
Postal country
Street country
Postal postcode
Street postcode
Last name of the contact person
First name of the contact person
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_CREATE_OR_UPDATE_SUPPLIERTool to create a new supplier or update an existing supplier in Ascora. Use when you need to add a new supplier with contact and address details, or modify an existing supplier's information by providing the supplierId.
Input parameters
The supplier's fax number
The name of the supplier
Additional notes about the supplier
The supplier's phone number
The supplier's mobile number
The unique identifier for the supplier. Required when updating an existing supplier, omit when creating a new supplier.
Postal address line 1
Postal address line 2
Postal address state
Street address line 1
Street address line 2
Street address state
The supplier's email address
Postal address suburb
Street address suburb
The supplier's business number (ABN/ACN)
The expense account code for this supplier
Postal address postcode
Street address postcode
The supplier's reference number
The last name of the contact person
The first name of the contact person
The number of days for invoice due date calculation
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_CREATE_QUOTATIONCreates a new quotation/enquiry in Ascora for a customer. Use this tool when you need to submit a quote request with customer details (name, email, contact info), optional address information, work description, and custom fields. Returns a unique entity ID for the created enquiry that can be used to track or reference the quotation.
Input parameters
Customer's email address
Customer's landline phone number
Customer's mobile phone number
Customer's last name
Customer's first name
Name of the customer's company
First line of the address, e.g., street and number
Second line of the address, e.g., unit or suite
State or territory of the address, e.g., 'WA', 'NSW'
List of custom field name/value pairs to include with the request
Suburb or city of the address
Country of the address
Postal code for the address
Description of the quote request
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_DELETE_CUSTOMERTool to delete a specific customer by ID. Use when you need to remove a customer after confirming its existence.
Input parameters
Unique identifier of the customer to delete
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_CONTACTTool to retrieve details of a specific contact by their unique identifier. Use when you need to fetch information about a contact including their name, contact details, address, and customer association.
Input parameters
The unique identifier (UUID) of the contact to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_CUSTOMERTool to retrieve details of a specific customer by their unique identifier. Use when you need to fetch information about a single customer including contact details, addresses, and status.
Input parameters
The unique identifier (UUID) of the customer to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_CUSTOMERSRetrieves all customers from the Ascora system. Returns a list of customer records including contact information (name, email, phone) and address details (street, city, state, postcode, country). This is a read-only operation that requires authentication via API key. Useful for syncing customer data, creating customer lists, or verifying customer information exists in the system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_INVENTORY_CATEGORIESRetrieves all inventory categories used to organize supplies and kits in Ascora. Returns a paginated list of categories with their IDs, names, and numeric identifiers. Use this when you need to list available inventory categories or reference category information for organizing inventory items.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_INVENTORY_KITSRetrieves all inventory kits from Ascora. Returns a paginated list of kit items that bundle multiple supplies together. Use this when you need to list available inventory kits or access kit details for quoting, job planning, or inventory management.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_INVENTORY_SUPPLIESRetrieves all inventory supplies with pricing and stock information from Ascora. Returns a paginated list of supply items. Use this when you need to list available inventory supplies or access supply details including pricing and stock levels.
Input parameters
Page number for pagination (1-based).
Number of records per page, between 1 and 1000.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_JOBRetrieves details of a specific job by its unique identifier. Returns comprehensive job information including job number, name, status, customer details, dates, and other job-specific data. Use this when you need to fetch detailed information about a particular job in the Ascora system.
Input parameters
The unique identifier of the job. Accepts both numeric IDs (e.g., '1') and UUID format (e.g., '00000000-0000-0000-0000-000000000001').
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_JOBSRetrieves a paginated list of jobs from Ascora with optional filtering by job type, status, secondary status, and date range. Returns job details including job number, name, status, customer information, and assignment details. Use this when you need to list, search, or monitor jobs in the Ascora system.
Input parameters
Page number for pagination (1-based).
Filter jobs created on or before this date (ISO 8601 date, YYYY-MM-DD).
Filter by job type, e.g., 'Installation' or 'Service'.
Number of jobs per page, between 1 and 1000.
Filter by main job status, e.g., 'Open', 'Closed'.
Filter jobs created on or after this date (ISO 8601 date, YYYY-MM-DD).
Filter by secondary status of the job.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_QUOTE_LABOUR_ROLESRetrieves labour roles available for use in quotes from Ascora. Use this when you need to list available labour roles with their hourly rates for quotation purposes.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_QUOTESRetrieves a paginated list of quotes from Ascora with optional filtering by status, date range, or customer. Returns quote details including quote number, customer information, status, creation date, and total amount. Use this when you need to list, search, or monitor quotes in the Ascora system.
Input parameters
Page number for pagination (1-based).
Filter by quote status, e.g., 'Draft', 'Sent', 'Accepted', 'Declined'.
Filter quotes created on or before this date (ISO 8601 date, YYYY-MM-DD).
Number of quotes per page, between 1 and 1000.
Filter quotes created on or after this date (ISO 8601 date, YYYY-MM-DD).
Filter by customer ID to retrieve quotes for a specific customer.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_QUOTE_STANDARD_SECTIONSRetrieves standard sections that can be used in quotes. Returns a list of pre-configured standard sections that can be included in quotations. This is a read-only operation that requires authentication via API key. Use when you need to list available standard sections for quote generation or to verify what sections exist in the system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_QUOTE_STANDARD_STAGESRetrieves standard stages that can be used in quotes for progress tracking. Use this when you need to list available quote stages, display progress tracking options, or reference standard stages for quote management. Returns all configured standard stages in the Ascora system.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_SUPPLIERTool to retrieve details of a specific supplier by ID. Use when you need to fetch supplier information including contact details, address, and business information.
Input parameters
The unique identifier (UUID) of the supplier to retrieve
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_SUPPLIER_INVOICESRetrieves supplier invoices from Ascora with optional pagination. Returns invoice details including invoice number, supplier name, dates, amounts, and status. Use this when you need to list, search, or monitor supplier invoices in the Ascora system.
Input parameters
Page number for pagination (1-based).
Number of supplier invoices per page, between 1 and 1000.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_GET_SUPPLIERSRetrieves a list of suppliers from the Ascora system. Returns supplier details including name, contact information (email, phone), address details, ABN, and activity status. Use this when you need to list or search for suppliers in the Ascora system.
Input parameters
Page number for pagination (1-based).
Number of records per page, between 1 and 1000.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_SEARCH_JOBSSearch for jobs by various criteria including job number, customer, or address. Use this when you need to find specific jobs based on identifiers or search terms rather than filtering by status or type.
Input parameters
Page number for pagination (1-based).
Search for jobs by address. Supports partial matching.
Search for jobs by customer name. Supports partial matching.
Number of jobs per page, between 1 and 1000.
Search for a specific job by its job number.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
ASCORA_UPLOAD_ATTACHMENTTool to upload an attachment to an entity (quote, job, customer, etc.) in Ascora. Use when you need to attach files like documents, images, or plans to existing entities in the system.
Input parameters
The file to upload as an attachment.
The unique identifier (UUID/GUID format) of the entity to attach the file to. Must be a valid UUID from the Ascora system.
The type of entity to attach the file to. Must be one of: Customer, Job, Quote, Enquiry, Invoice, PurchaseOrder, or Asset.
Output
Data from the action execution
Error if any occurred during the execution of the action
Whether or not the action execution was successful or not
No publicly available marketplace agent is found using this tool yet. There are 53 agents privately built on Nagent that already use Ascora.
Build on Nagent
Connect Ascora to any Nagent agent in minutes — no API key management, no boilerplate. Just configure and deploy.
The five questions agent builders ask before adopting a new integration.
Open the External Integrations panel inside Nagent (app.nagent.ai/externalIntegration), find Ascora, and click "Connect Now." You'll authenticate with an API key — Nagent handles credential storage and refresh automatically. Once connected, Ascora is available to any agent in your workspace.
No. Nagent provides no-code integration for every tool. Once Ascora is connected, you configure its 23 actions directly in the agent builder UI — no API calls, no boilerplate, no schema management.
Helix — Nagent's agentic agent builder — lets you drop Ascora steps into any workflow visually. Pick an action (e.g., one of those listed above), fill in the inputs (Helix knows the required vs. optional schema for each parameter), and connect it to upstream/downstream steps. Triggers run as the entry point of an agent, so when a Ascora event fires, the agent kicks off automatically.
Every Ascora action and trigger ships with a fully-typed schema — input parameters with name, type, required flag, and description, plus the output payload shape. The schemas are documented in the sections above. Helix uses these schemas to validate your configuration at build time and to type-check the data flowing between steps.
Yes. While Ascora ships with 23 pre-built crm actions, you can layer custom logic around them inside Helix — pre/post-processing steps, conditional branches, retries, or stitching Ascora together with other connected tools. For deeper customization, talk to our team about Nagent's Agentic AI Lab — forward-deployed engineers who build Ascora-based workflows tailored to your business.