Productivity · Integration
Ascora
Add Ascora to your product for your customers, and give your AI agents governed access to it.
Ascora is job management software for Australian trade and field service businesses, so Productivity is the closest fit: jobs are work items with assigned technicians and scheduled dates, though the product also carries quotes and invoices. The API at api.ascora.com.au requires an Authorization token header and says so in plain text on an unauthenticated call, returning a 400 with a readable message rather than a 401, so status-code-only error handling will misclassify a missing credential. The token is issued per Ascora company file, which means a customer with several trading entities has several credentials and job ids are only unique within one of them. A job carries scheduled appointments, assigned staff, materials and attachments as related collections rather than fields, so building a useful job view is several calls, and job status transitions are constrained by the workflow the customer has configured rather than being freely settable. Ascora also syncs to accounting packages, so invoices written through the API can be locked once they have been pushed downstream. fastn keeps each customer's Ascora token and company scope separate and maintains the integration as endpoints change.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Ascora company so jobs raised in your product reach the field team's schedule
Show job status, assigned technician and scheduled date next to the asset or property record you already hold
Push completed work back as a quote or invoice draft rather than asking office staff to re-enter it
Give a customer a view of jobs scheduled this week that still have no technician assigned
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which jobs are overdue against their scheduled date for a given tenant
Have an agent create a job from an approved request and report the id it was given, with the write audited per tenant
Let an agent summarise the quotes issued last month and which converted to jobs
Example prompt
Which Ascora jobs are scheduled for this week and are any still unassigned?
Set up Ascora in 4 steps
- 01Enable the Ascora connector from your fastn dashboard.
- 02Have each customer authorise their own Ascora account, so calls run under their credentials rather than a shared key.
- 03Decide which work items, assignees and due dates your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Ascora integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Ascora integration without building it. Your customers connect their own Ascora account inside your product and work their work items, assignees and due dates there, with no per-customer code on your side.
- Handle the part that actually costs time: every team configures its own fields, statuses and workflow stages. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Ascora update is not your on-call problem.
- One integration serves your product and your agents. The same governed Ascora connection powers in-product features and gives AI agents scoped, audited access, so you keep work items in step with what happens in your product without wiring it twice.
Used by these teams
Compare with
Jira
Asana
ClickUpOften used alongside
Tools the same teams tend to run next to Ascora, across other categories.
Notion
Box
Docusign
AWS Simple Storage ServiceAscora integration FAQ
How do I add an Ascora integration to my product?
Enable the Ascora connector in your fastn dashboard, then let each customer authenticate their own Ascora account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Ascora client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Ascora account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Ascora account and only ever sees their own work items, assignees and due dates. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Ascora integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which jobs are overdue against their scheduled date for a given tenant
Who maintains the Ascora integration?
fastn does. When Ascora changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create and update work in Ascora automatically?
Yes. Items can be created, updated, assigned and transitioned from your product, and changes made in Ascora can trigger your workflows in return.
Does it adapt to each team's own Ascora setup?
Yes. However a team has configured Ascora, whether that is custom fields, statuses and workflow stages or its own calendars and working hours, those are mapped per customer, so an unusual setup works without custom code from you.
What can I build with the Ascora integration?
A common starting point: let a customer connect their own Ascora company so jobs raised in your product reach the field team's schedule. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Ascora integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Ascora does not change your per-connector cost. You can start free with 3 connected accounts.
Add Ascora to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.