Before you connect
- A Burki workspace administrator account, a saved assistant and permission to authorize the intended Jobber business.
- An eligible Jobber account with access to the Burki app. If Jobber blocks installation, contact Burki support.
- For service requests, an existing client with an exact matching service property in Jobber.
Review Burki usage pricing and your provider’s plan before a live test. Telephone calls, phone numbers and optional SMS can add charges; this guide does not promise a free provider plan.
Access and permissions
The connection requests Clients and Requests read/write access. Burki stores the connection securely at workspace level.
Choose client lookup, client creation and service-request permissions separately in each assistant’s Actions tab.
Connect and configure
Authorize Jobber
Open Integrations, select Jobber and choose Connect Jobber. Check the business on the authorization screen, approve the required access and return to Burki.
Check the connection
Confirm the connected business name and choose Test connection. This read-only check creates no clients or requests.
Enable assistant actions
Open a saved assistant’s Actions tab and select the Jobber actions it needs. Instruct it to confirm contact details and the service address before saving.
Test the workflow
Browser practice uses simulated client and request results. It does not access or change Jobber.
Use an authorized test client for a real acceptance test. Verify the client, property, service issue and request in Jobber. Requests are unscheduled; they do not book visits or dispatch technicians.
Troubleshooting
- Reconnect required
- A workspace administrator should reconnect Jobber and verify the business identity before enabling live actions.
- Client or address cannot be matched
- Confirm the exact email and service address. Ask staff to resolve duplicate clients, missing properties or ambiguous addresses in Jobber.
- Request outcome is uncertain
- Inspect Jobber before retrying. A timeout is not proof that no request was saved; Burki does not automatically retry an uncertain write.
Disconnect safely
- Remove the Jobber actions from an assistant to stop its access.
- Choose Disconnect Jobber in workspace Integrations to disable workspace actions and request provider revocation.
- If revocation cannot be confirmed, remove Burki from connected apps in Jobber. Existing clients and requests remain in Jobber.
Data and support
Confirmed contact details, service addresses and request details are sent to Jobber. Burki records the integration outcome for call review. Never put credentials in assistant instructions.
Burki’s privacy policy explains retention and data requests. Your workspace settings and applicable terms govern your account. Disconnecting an integration is separate from requesting deletion. See the terms of service for service conditions.
Need help with this connection?
Include the provider, workspace name, approximate time and a redacted error message. Never send API keys, authorization codes, payment links, card details or customer call content.
Contact Burki support