Integrations
Works with the tools your teams already use
hey.space imports projects, tasks, tickets and deals from 22 tools, including Asana, Jira, Zendesk and Salesforce. AI then matches your team’s activity to that work, so the report shows time and cost per task, ticket or deal, not just per app.
30-minute call. We’ll show what a 2-week pilot on your team’s data would reveal.
How integrations feed your report
- 1
Connect a tool
Someone on your team connects the tool to TimeCamp with read-only access.
- 2
Work becomes tasks
Projects, tasks, tickets and deals are imported into TimeCamp as tasks, in one direction. New items arrive within a few hours.
- 3
AI matches the activity
AI matches the activity from TimeCamp’s desktop app to those tasks, so time and cost show up per task, ticket or deal.
Project and task management
13 tools
| Tool | What becomes a task | Help article |
|---|---|---|
| Databases as tasks, their items as subtasks | Help article | |
| Boards as tasks, lists and cards as subtasks | Help article | |
| Projects as tasks, lists as subtasks | Help article | |
| Boards as tasks, lists and items as subtasks | Help article | |
| Spaces as tasks, lists and tasks as subtasks | Help article | |
| Workspaces and sheets as tasks, their projects and tasks as subtasks | Help article | |
| Workspaces as tasks, projects, folders and tasks as subtasks | Help article | |
| Projects as tasks, tasks as subtasks | Help article | |
| Projects as tasks, lists and tasks as subtasks | Help article | |
| Workspaces as tasks, apps and items as subtasks | Help article | |
| Projects as tasks, lists and tasks as subtasks | Help article | |
| Projects as tasks, lists and tasks as subtasks | Help article | |
| Projects as tasks, lists and tasks as subtasks | Help article |
Engineering
4 tools
| Tool | What becomes a task | Help article |
|---|---|---|
| Projects as tasks, epics and issues as subtasks; optional time export as worklogs | Help article | |
| Repositories as tasks, issues, branches and pull requests as subtasks | Help article | |
| Projects as tasks, issues and branches as subtasks | Help article | |
| Workspaces as tasks, projects and work items as subtasks | Help article |
For Jira, you can also export time back to Jira as worklogs; it is optional. Engineering teams can read our guides to Jira time in status, the cumulative flow diagram and a Jira dashboard for flow metrics.
Customer support
2 tools
| Tool | What becomes a task | Help article |
|---|---|---|
| Tickets as tasks | Help article | |
| Tickets as tasks | Help article |
Sales and CRM
2 tools
| Tool | What becomes a task | Help article |
|---|---|---|
| Opportunities and cases as tasks | Help article | |
| Projects, tasks, contacts, organizations and leads as tasks | Help article |
Team communication
1 tool
| Tool | What becomes a task | Help article |
|---|---|---|
| Public channels as tasks | Help article |
Descriptions from TimeCamp help articles, checked on November 16, 2026.
What you get: time and cost per task, ticket and deal
With your tools connected, the report shows what each kind of work really costs, including the time spent outside the tool it belongs to.
Asana · Content update task
2.1 h
31% of the time spent outside Asana
Zendesk · Support ticket
0.4 h
1 in 5 tickets also touches Jira
Salesforce · Won opportunity
6.4 h
42% of deal time in email and calls
Jira · Bug fix
3.2 h
Plus 1.1 days waiting in review
Illustrative figures. This preview uses example numbers in the format of a real report. It will be replaced with anonymized data from TimeCamp’s own teams. How the figures are built
Privacy and access
Integrations read work structure only, and only what the person who connects them can already see.
Read-only, one direction
Data flows from your tool to TimeCamp. The only write back is the optional time export to Jira as worklogs.
Only what you can see
Only items available to the person who connects the tool are imported.
No private Slack channels
Slack imports public channels only. Private channels are never imported.
Team-level results
Reports show teams, tasks, tickets and deals, not scores for individuals.
See what your team could automate
Start with a 30-minute call. If it’s a fit, a 2-week pilot on your team’s data shows your biggest time drains and a ranked list of automation opportunities.
30-minute call. We’ll show what a 2-week pilot on your team’s data would reveal.