WebWork’s Azure DevOps integration connects your WebWork workspace to Azure DevOps with full two-way sync. It supports both Azure DevOps Services (via OAuth) and on-premises Azure DevOps Server (via Personal Access Token), and a single workspace can connect multiple ADO organizations at once.
Connecting Azure DevOps
- Go to Integrations → Azure DevOps.
- Click Enable.
- Connect your account:
- If you’re on Azure DevOps Services (cloud), sign in and grant WebWork access through OAuth.
- If you’re on Azure DevOps Server (on-premises), connect using a Personal Access Token instead.
- To connect another organization later, repeat the process; a single WebWork workspace can have multiple ADO organizations connected at the same time.

Once connected, you’ll land on the integration page, with three tabs: Members, Projects, and Auto-Sync.
Members
Your ADO members are automatically invited to WebWork, with role mapping applied so permissions carry over sensibly. The Members tab shows each person’s name, email, and import Status. Members already registered in WebWork with a matching email are synced instead of duplicated.

Projects
Go to the Projects tab and select which ADO projects to import, including their area paths and iterations — so you’re not forced to bring in more structure than you actually use. Toggle With tasks on for a project to import its work items along with it.
Work items of all standard types: Epic, Feature, User Story, Task, and Bug, are imported, and each one keeps the state it had in Azure DevOps.
Click Import once you’ve made your selections. Imported projects show the Azure DevOps icon for easy recognition.

Auto-Sync
On the Auto-Sync tab, under Syncing Data from Azure DevOps, set the sync behavior for Projects and Tasks independently; choose Auto-sync & auto-remove to have items created, updated, or removed in Azure DevOps reflected in WebWork too. The tab shows the last sync time for each.
Once connected, webhooks keep WebWork up to date in real time: when a work item’s state, assignee, or fields change in Azure DevOps, WebWork reflects it right away.
Under Sending Data to Azure DevOps:
- Send tracked time data from WebWork — time tracked in WebWork is pushed to the work item’s Completed Work field, with Remaining Work decremented automatically.
- Two-way sync (push to Azure DevOps) — with this on, you can create ADO work items directly from WebWork through the task-creation UI and project picker, the same way the ClickUp integration works. Edits made in WebWork to a task’s title, description, dates, and assignee are written back to the matching ADO work item, and status changes in WebWork update the corresponding ADO work-item state.

Was this article helpful?
Thanks for your feedback.