Skip to content

Integration · Field service

dataforce.com.au

Connect Claude & ChatGPT to Dataforce ASAP

Ask your AI what is booked for a customer, which appointments are on a job, or to book a new appointment in Dataforce ASAP. It can create and update customers and jobs, add appointments with a work type and fieldworker, mark appointments completed and keep your to-do list up to date. Scheduling questions get answered without clicking through screens.

Connect Dataforce ASAP free

Free plan, no credit card. Takes about a minute.

Try asking

  • “What appointments does customer 5812 have?”

    The AI lists all appointments for that customer, with job, work type, fieldworker, dates and status.

  • “Book a service visit for Tom Baker at 14 King Street next Tuesday.”

    It looks up the client, agent and work type, then books the appointment in one step. ASAP creates the customer, job and appointment together.

  • “Add an appointment to job 20417 and give it to the fieldworker who is free.”

    It lists your fieldworkers and work types and adds the appointment to the job with the fieldworker, date and instructions you confirm.

What your AI can do

Appointments

Book, add, read, search, complete and cancel appointments, with work types, fieldworkers and cancellation reasons.

Jobs and customers

Search, create and update customers and jobs, find a customer by your own reference, and reassign a job to another agent.

Setup lists and to-dos

List clients, agents, fieldworkers and work types, and read and create to-dos.

  • “Mark appointment 88321 as completed today with a short note.”

    It marks the appointment completed with the completion date and your comment.

  • “Cancel job 20417, the customer moved.”

    It lists the job cancellation reasons, picks the one you choose and cancels the job with a comment.

  • “Create a to-do for the office to call back the Smith job.”

    It creates a to-do with a title, description and status, and can assign it to an operator.

98 tools for Dataforce ASAP

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

  • book_appointmentVisible to othersBook an appointment in one step from `body`: customer details and address (or `customerId`), `clientId`, `agentId`, `workTypeId`, `activityDate` and any answers. This creates the customer, job and appointment in ASAP together.
  • cancel_appointmentDeletesCancel an appointment by `appointment_id`, with an optional `cancellation_reason_id` (from list_appointment_cancellation_reasons) and `comment`. Treat this as irreversible.
  • cancel_jobDeletesCancel a job by `job_id`, with an optional `cancellation_reason_id` (from list_job_cancellation_reasons) and `comment`. Treat this as irreversible.
  • complete_appointmentVisible to othersMark an appointment as completed by `appointment_id`, with an optional `actual_completed_date` and `comment`.
  • create_appointmentChanges dataAdd an appointment to an existing job, given `job_id` and `work_type_id`, plus an optional `fieldworker_id`, `scheduled_date`, `duration` and `job_instruction`.
  • create_appointment_questionChanges dataCreate a new question for a appointment.
  • create_customerChanges dataCreate a customer from `body` fields such as firstname, surname, companyName, email, mobilePhone and the address fields (streetNo, streetName, streetType, suburb, state, postCode). Search first to avoid duplicates.
  • create_customer_agent_createChanges dataCreate a new customer. Required: company name, email, post code or client ids. Search customers first to avoid duplicates.
  • create_customer_customer_questions_saveChanges dataCreate a new customer for a customer. Search customers first to avoid duplicates.
  • create_documentChanges dataCreate a new document. Required: form id, category id, description or file.
  • create_document_file_create_otherChanges dataCreate a new document. Required: category id, description or file.
  • create_document_file_create_photoChanges dataCreate a new document. Required: stamp, category id, description or file.
  • create_fieldworker_setup_codeChanges dataCreate a new setup code for a fieldworker.
  • create_jobChanges dataCreate a job for a customer, given `customer_id`, `client_id` and `agent_id`, plus an optional `source_id`, `sales_pipeline_stage_id` or `tracking_code`. Appointments are then added to the job.
  • create_paymentChanges dataCreate a new payment. Required: transaction date or transaction amount.
  • create_project_job_questions_saveChanges dataCreate a new project for a project. Search projects first to avoid duplicates.
  • create_questionChanges dataCreate a new question.
  • create_todoChanges dataCreate a to-do with a `title` and `description`, an optional `status` (New, Pending, In Progres, Completed, On Hold) and `assigned_operator_id`.
  • delete_documentDeletesPermanently delete a document by document id. Destructive action; may require approval.
  • get_appointmentGet one appointment by `appointment_id`, with its job, work type, fieldworker, dates and status.
  • get_calculationGet one calculation by calculation id.
  • get_customerGet one customer by ASAP `customer_id`, including contact details and address.
  • get_customer_agent_getGet one customer by customer id.
  • get_customer_by_refGet one customer by your own customer reference (`customer_ref`) instead of the ASAP ID.
  • get_customer_client_getGet one customer by customer id.
  • get_customer_clients_agent_get_agentGet one customer by customer id.
  • get_customer_work_types_agent_get_agentGet one customer by customer id.
  • get_documentGet one document by document id.
  • get_fieldworkerGet one fieldworker by fieldworker id.
  • get_invoiceGet one invoice by invoice id.
  • get_jobGet one job by `project_id` (the job ID), with its customer, client, agent and status.
  • get_paymentGet one payment by payment id.
  • get_payment_ledger_payment_link_getGet one payment by payment id.
  • get_postcodeGet one postcode by postcode.
  • get_productGet one product by product id.
  • get_product_reasonsGet one product by instance.
  • get_questionGet one question by question id.
  • get_question_blockGet one question block by question block id.
  • get_street_typeGet one street type by street type id.
  • get_submissionGet one submission by submission id.
  • get_suburbGet one suburb by suburb id.
  • get_supplierGet one supplier by supplier id.
  • get_unitGet one unit by unit id.
  • get_warehouseGet one warehouse by warehouse id.
  • get_work_typeGet one work type by work type id.
  • list_agentsList the agents with their IDs, needed when creating or reassigning jobs.
  • list_appointment_answersList answers for a appointment.
  • list_appointment_auditsList audits for a appointment.
  • list_appointment_calculationsList calculations for a appointment.
  • list_appointment_cancellation_reasonsList the reasons that can be given when cancelling an appointment, with their IDs.
  • list_appointment_documentsList documents for a appointment.
  • list_appointment_invoicesList invoices for a appointment.
  • list_appointment_questionsList questions for a appointment.
  • list_appointment_submissionsList submissions for a appointment.
  • list_appointment_tagsList tags for a appointment.
  • list_calculationsList calculations.
  • list_categoriesList categories.
  • list_clientsList the clients (the programs or companies you do work for) with their IDs, needed when creating jobs.
  • list_customer_appointmentsList all appointments for one customer by `customer_id`.
  • list_customer_jobsList all jobs for one customer by `customer_id`.
  • list_customer_projects_jobs_get_by_customer_refList projects for a customer.
  • list_customersList customers for a customer.
  • list_customers_customer_consent_getList customers for a customer.
  • list_fieldworkersList the fieldworkers (technicians) with their IDs, for assigning appointments.
  • list_hazard_codesList hazard codes.
  • list_job_appointmentsList all appointments on one job by `job_id`.
  • list_job_cancellation_reasonsList the reasons that can be given when cancelling a job, with their IDs.
  • list_job_source_associatesList job source associates.
  • list_job_sourcesList job sources.
  • list_productsList products.
  • list_project_documentsList documents for a project.
  • list_project_quotesList quotes for a project.
  • list_projectsList projects for a project.
  • list_question_answersList answers for a question.
  • list_question_blocksList question blocks.
  • list_questionsList questions.
  • list_questions_questions_getList questions.
  • list_refundreasonsList refundreasons.
  • list_sales_pipelinesList sales pipelines.
  • list_street_typesList street types.
  • list_submission_appointmentsList appointments for a submission.
  • list_suburbsList suburbs.
  • list_suppliersList suppliers.
  • list_todosList the to-dos (tasks) in ASAP, with title, status and assigned operator.
  • list_unitsList units.
  • list_warehousesList warehouses.
  • list_work_typesList the work types with their IDs, needed when creating or booking appointments.
  • refund_refundMoves moneyRefund a refund (instance). Financial or irreversible action; may require approval.
  • search_appointmentsChanges dataSearch appointments with `filter_groups`, a list of groups, each with `filters` of {propertyName, operator, value} where operator is EQ, NEQ, LT, LTE, GT or GTE. Page with `limit` and `after`; leave `sorts` out.
  • search_customersChanges dataSearch customers with `filter_groups`, a list of groups, each with `filters` of {propertyName, operator, value} where operator is EQ, NEQ, LT, LTE, GT or GTE. Page with `limit` and `after`; leave `sorts` out.
  • search_jobsChanges dataSearch jobs with `filter_groups`, a list of groups, each with `filters` of {propertyName, operator, value} where operator is EQ, NEQ, LT, LTE, GT or GTE. Page with `limit` and `after`; leave `sorts` out.
  • search_submissionsChanges dataSearch submissions. Use this to find existing submissions before creating a new submission.
  • update_customerChanges dataUpdate a customer by `customer_id` with the `body` fields to change (name, email, phones, address). Only the fields you pass change.
  • update_customer_agent_updateChanges dataUpdate an existing customer identified by customer id. Only the fields you pass are changed.
  • update_customersVisible to othersUpdate an existing customer identified by customer id. Only the fields you pass are changed. Has effects visible outside this system.
  • update_fieldworkerChanges dataUpdate an existing fieldworker identified by fieldworker id. Only the fields you pass are changed.
  • update_jobChanges dataUpdate a job by `project_id`: reassign it to another `agent_id` or add a `comment`.
  • update_paymentChanges dataUpdate an existing payment identified by payment id. Only the fields you pass are changed.

Set up in three steps

  1. 1

    Pick the app

    Create a free HeyMyApps account and choose Dataforce ASAP from the app list.

  2. 2

    Paste your key

    Paste your ASAP API client ID, API client secret and ASAP instance name. In ASAP go to Admin, create or edit a user and set Access Type to 'API User (Read Only)' or 'API User (Read/Write)', then save to see the API credentials. On the user's Program Access tab, apply a role to each program the API user needs.

  3. 3

    Add the link to your AI

    You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:

    1. Click your name, then Settings › Connectors › Add custom connector.
    2. Paste your link as the Remote MCP server URL.
    3. Switch it on from the + menu in a chat.

Questions

What can the AI do in Dataforce ASAP?

The AI can read and search customers, jobs and appointments, and list clients, agents, fieldworkers, work types, cancellation reasons and to-dos. It can create and update customers and jobs, add and book appointments, mark appointments completed, cancel appointments and jobs, and create to-dos.

Does the AI see my Dataforce ASAP credentials?

No. Your API client ID and client secret are encrypted at rest and never shown to the AI. After you save them, they are not shown again, not even to you. The AI only sees the results of the tools it calls.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can start read-only. Cancelling an appointment or a job cannot be undone, and booking or completing appointments changes your schedule, so these can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT go to Settings › Apps & Connectors › Advanced and turn on Developer mode, then add your HeyMyApps link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector), Cursor and other MCP clients.

What does it cost?

Dataforce ASAP connects with OAuth, and OAuth connections need the HeyMyApps Pro plan or above. HeyMyApps also has a free plan with no credit card, but it does not include this connection. Paid plans bill per completed task. You also need your own ASAP account.

Should I use a read-only API user?

If you only want answers, yes. ASAP lets you create an API user with Access Type 'API User (Read Only)' or 'API User (Read/Write)'. A read-only user cannot book, change or cancel anything, on top of the tools you switch on in HeyMyApps. The program roles you apply on the Program Access tab also limit what the API user can reach.

Let your AI work in Dataforce ASAP today.

Start free. Your key stays encrypted, and you decide what the AI may do.

Connect Dataforce ASAP free

HeyMyApps is not affiliated with Dataforce ASAP. Product names are trademarks of their owners.