Fiix
Planned: close work orders and create requests in Fiix (Rockwell Automation) by text.
Not available yet. This page describes what's planned for Fiix. 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 Fiix:
| You text | What would happen in Fiix |
|---|---|
| “Replaced the seal on Pump 7, 1 hr” | Closes the work order with labor |
| (photo) Belt fraying on line 2 | Creates a work request with the photo |
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 customer’s Fiix instance and API access. Enterprise subscribers can request a sandbox through their Fiix representative. Credentials and user permissions are specific to the instance. Fiix developer guide.
Developer setup — once
Section titled “Developer setup — once”- Use the official SDK or implement the documented request-signing protocol. Fiix’s application/access/secret keys are not a generic Bearer token. No-SDK protocol.
- Implement encrypted key storage, correct instance routing and API error handling.
- Map assets, sites, users and work-order status IDs for the pilot.
Customer setup — repeat for each instance
Section titled “Customer setup — repeat for each instance”- An admin signs in to the intended test or production instance.
- Open Settings → Connect Management → MA Connect API Application Settings.
- Click New API Application, enter the description and create it.
- Securely save the Application Key, Access Key and Secret Key; the secret cannot be retrieved later.
- Restrict the associated account’s permissions to the intended work. API access inherits that account’s access.
- Configure the customer’s own base URI ending in
/api/; never leave the sample or another customer’s instance URL in place.
These are the credential and instance steps in the Fiix developer guide.
Verify write access
Section titled “Verify write access”Read one test asset and create an agreed work order against it. Read it back and inspect the Fiix UI for site, status and assignee. Check the API response’s error data, not only its HTTP status. A ping alone is not proof of asset access or write permissions.
Disconnect and troubleshoot
Section titled “Disconnect and troubleshoot”Have the admin disable/remove the dedicated API application or revoke its credentials using the instance’s supported management procedure. Confirm with Fiix support if those controls are unavailable. Remove local keys and verify old signed requests fail. For authentication errors, check all three keys, instance URL and signing implementation before changing user permissions.
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.