Integrations
Use Integrations to connect external applications from My Profile, and let administrators manage webhooks and organization sign-in providers.
Overview
Integrations let you connect services used with time tracking, leaves, projects, or related tools, and sync data where supported (for example Keka leaves or Outlook calendar events).
| Area | Where to open it | Purpose |
|---|---|---|
| My Profile integrations | My Profile → Integrations | Connect or disconnect providers for your account |
| Webhook subscriptions | Administration → Webhook Subscriptions | Send outbound event notifications |
| Identity providers | Administration → Tenant Settings | Configure organization sign-in providers |
Some integrations may appear as unavailable until your organization enables them.
How to access
My Profile → Integrations
Administrators can also open:
- Administration → Webhook Subscriptions
- Administration → Tenant Settings (identity providers)
What you can do
The catalog can include providers such as:
| Provider | How you typically connect |
|---|---|
| Outlook | Sign-in window |
| Keka | Connect flow; leave sync may run after connect |
| Azure DevOps | Project, DevOps project name or URL, and personal access token |
| ChatGPT, Claude, GitHub Copilot, Cursor | API key or token where enabled |
When you connect, you may choose how the license is allocated (for example to your company or to a client). If you allocate to a client, select the client when prompted.
Do not share API keys or personal access tokens in tickets or screenshots.
Administrators can create webhook subscriptions, review events, activate subscriptions, and run test publishes where those actions appear. Identity provider settings control how users sign in. See Authentication.
Step-by-step workflow
- Open My Profile → Integrations.
- Select an available provider and choose Link or Connect.
- Choose license allocation and complete the sign-in window, or enter the API key or Azure DevOps fields.
- Connect, then confirm the provider card shows as connected.
- Later, disconnect when needed and confirm.
For Outlook, allow popups for In Time PRO if the browser blocks the sign-in window.
Expected result
The provider card shows as connected. Optional follow-up actions may run, such as Keka leave sync or Outlook calendar events being saved for your user. Disconnect removes the connection after you confirm.
If the sign-in window stays open too long, the product may time out and ask you to retry.
Common validations
| Situation | What you see |
|---|---|
| API key missing | API key is required |
| Client allocation without a client | Client required message |
| Azure DevOps fields incomplete | Project / DevOps fields required messages |
| Popup blocked | Popup blocked guidance |
| Sign-in takes too long | Timed-out guidance; try again |
| Catalog or connect failure | Load failed or connect failed message |
| Disconnect | Confirmation before disconnect |