Limble
Planned: close tasks and work orders and create requests in Limble by text.
Not available yet. This page describes what's planned for Limble. Ask in your thread and we'll text you when it's ready.
Status: planned — not available to connect in Tack yet. These steps prepare the integration; creating vendor credentials does not enable it in the app.
Planned workflows
Section titled “Planned workflows”Planned for Limble:
| You text | What would happen in Limble |
|---|---|
| “Finished the PM on Compressor 1” | Completes the task |
| (photo) Leak at pump 3 | Creates a work request |
These are intended workflows, not a guarantee that every operation is exposed by the vendor. Each must pass the API and permission checks below before release.
Before you start
Section titled “Before you start”Identify the organization’s Limble hosting region and confirm API entitlement. A Super Administrator is needed to generate API credentials.
Developer setup — once
Section titled “Developer setup — once”- Review the Limble API reference and choose the correct regional API base URL.
- Implement HTTP Basic authentication with the client ID and client secret, not an employee’s login password. Keep both in encrypted storage.
- Map task, asset, location and user IDs; identify the supported fields for the planned task creation/update workflow.
Customer setup — repeat for each organization
Section titled “Customer setup — repeat for each organization”- A Super Administrator opens Settings → Configuration → API Settings.
- Choose Generate API Keys and securely copy the client ID and secret. The secret is only displayed once.
- Confirm the regional API host: the reference lists default, Canada, Australia, Europe and 21 CFR hosts. Store the correct host with this customer’s credentials.
- Agree on the locations and operations Tack may use. If the credentials cannot enforce those limits themselves, the connector must enforce them; do not describe application filtering as a vendor permission boundary.
Follow the authentication and regional-host instructions rather than guessing the API URL from the browser address.
Verify write access
Section titled “Verify write access”Read a known asset, create a clearly labeled task linked to it and read the task back. Check location, assignee and priority in Limble. Verify the connector rejects a location outside the customer’s approved set. Keep completion and deletion separate from the initial creation test.
Disconnect and troubleshoot
Section titled “Disconnect and troubleshoot”Coordinate with the Super Administrator to revoke or regenerate credentials using the account’s API settings, then remove the stored pair. Check whether another integration shares the same pair before rotation. Confirm old credentials fail. Authentication failures may indicate the wrong regional host or an outdated secret rather than a missing task permission.
Who completes the work?
Section titled “Who completes the work?”An agent/developer can implement the connector, field mappings and automated checks. A customer administrator must authorize account access and permissions; the vendor must approve any restricted partner access. A business operator verifies the test records before production use. Follow the shared setup and release checklist for credential handling, approval gates and launch checks.
Setup guidance reviewed October 23, 2026. Vendor menus and entitlements can change; unresolved details are called out above.