If your team already uses Zapier to connect the tools you run daily, the TeamWork Zapier integration puts your CMMS into those same workflows — no custom code, no IT project required.
Most maintenance teams get a work order request through a half-dozen different channels: a Google Form submission, a help desk ticket, an email, a sensor alert from a monitoring tool. Without a direct connection to your CMMS, someone has to manually copy that request into TeamWork. The Zapier integration closes that gap by letting other apps create and update TeamWork work orders automatically.
What the TeamWork Zapier integration does
The integration exposes triggers and actions that you combine in Zapier’s workflow builder (called “Zaps”):
Triggers — things that happen in TeamWork that can start a Zap:
- New work order created — fires when any work order is opened in TeamWork; use it to post a Slack message, add a row to a Google Sheet, or create a task in your project management tool
- Work order status changed — fires when a work order moves from open to in-progress, on hold, or any other status; useful for updating records in connected systems
- Work order completed — fires when a work order is closed; log completions to a spreadsheet, notify a requester by email, or update a field in your CRM
Actions — things Zapier can do inside TeamWork:
- Create work order — lets any other app open a TeamWork work order; the action accepts all standard fields (title, priority, site, asset, assigned technician, description)
Common Zaps:
- Jotform or Typeform submission → create TeamWork work order
- Zendesk or Freshdesk ticket tagged “facilities” → create TeamWork work order
- Temperature or pressure alert from a monitoring platform → create high-priority TeamWork work order
- TeamWork work order completed → append row to Google Sheets maintenance log
- TeamWork work order status changed → post update to a Slack channel
How to set it up
- Log in to Zapier.com and create a new Zap.
- Search for “TeamWork” in the app list and select it as your trigger or action app.
- When prompted, authenticate by pasting your TeamWork API key (generated in Settings → API inside TeamWork).
- Choose your trigger or action, map the fields, and turn the Zap on.
No developer involvement is needed. If you want a more direct connection — or need to push high-volume events from IoT systems — the TeamWork REST API supports the same work order operations programmatically.
Who it’s for
The Zapier integration is a good fit for teams that already manage at least a few of their other business tools through Zapier, or for operations coordinators who need work orders to flow automatically from intake tools like forms or help desk software without waiting on a development resource.
It is not a replacement for the REST API if you’re building a custom internal tool or need bulk operations — in those cases, the API gives you more control and better performance.
See all TeamWork integrations or learn more about workflow automation features.
Start a free trial or connect your existing account.