Appointment buttons
Create a personal Core token for a Power Automate or Teams button that schedules an assigned ticket
Overview
Appointment buttons let a technician move one of their assigned tickets from Waiting on customer to Appointment scheduled from Power Automate or Microsoft Teams. The button runs with the technician's current Core access.
Each token is personal, workspace-bound, and shown only once. If the technician becomes inactive, loses ticket access, or the workspace is suspended, the token stops working. Revoke a token from Settings → Agents to disable it immediately.
Create a token
- Open Settings → Agents.
- Under Appointment buttons, enter a token name and choose Create token.
- Copy the token immediately. Core stores only its hash and cannot show it again.
- Store the token as a secret in Power Automate. Do not put it in a Teams message, URL, or log.
You can keep up to five active tokens. Revoke a token you no longer use before creating another.
Find an assigned ticket
Send a POST request to /api/technician-actions/tickets/search with the header:
Authorization: Bearer cta_your_token
Content-Type: application/json
The JSON body may include q, status, and limit (1–50):
{ "q": "Acme", "status": "waiting_customer", "limit": 25 }
The response contains only non-archived, non-merged tickets assigned to the token's technician. Save the ticket's id and updatedAt values for the schedule request.
Schedule the appointment
Send a POST request to /api/technician-actions/tickets/schedule with these headers:
Authorization: Bearer cta_your_token
Content-Type: application/json
Idempotency-Key: a-stable-unique-value-for-this-booking
Use the values returned by search:
{
"ticketId": "tkt000001",
"expectedUpdatedAt": "2026-09-29T18:00:00.000Z"
}
A successful response has status: "scheduled", the ticket ID, and the new update time. Reuse the same idempotency key when retrying the same booking after a timeout. Use a new key for a different ticket or update time.
Core rejects tickets assigned to someone else, archived or merged tickets, stale update times, and any transition other than Waiting on customer to Appointment scheduled. If a response is rate-limited, wait for the Retry-After interval before trying again.
Revoke a token
In Settings → Agents, choose Revoke beside the token and confirm. Existing Power Automate or Teams flows using it stop working immediately. Create a new token and update the flow if you need to rotate credentials.