Everhour Integration
Sync time entries with Everhour for advanced time tracking and reporting
Overview
The Everhour integration syncs time entries between Core and Everhour, enabling advanced time tracking features, detailed reports, and seamless billing workflows.
Setting Up
Prerequisites
- Everhour account with API access
- Core workspace with admin permissions
Getting Your API Key
- Log in to Everhour
- Go to Settings > Integrations
- Find or generate your API key
- Copy the key
Connecting to Core
- Go to Settings > Integrations > Everhour
- Click Connect
- Paste your Everhour API key
- Click Test Connection
- If successful, click Save
Project Mapping
Link Core projects to Everhour projects:
- Go to Project Mapping
- Select a Core project
- Choose the Everhour project
- Repeat for each project
- Save mappings
Sync Configuration
Sync Direction
Choose data flow direction:
| Mode | Description |
|---|---|
| Core to Everhour | Time logged in Core syncs to Everhour |
| Everhour to Core | Time logged in Everhour syncs to Core |
| Two-way | Time syncs both directions |
Sync Frequency
Configure how often sync occurs:
- Real-time: Immediate sync on entry
- Every 5 minutes: Near real-time
- Hourly: Batch sync
- Daily: End-of-day sync
What Syncs
| Core Field | Everhour Field |
|---|---|
| Time duration | Time |
| Ticket/task | Task |
| User | Team member |
| Date | Date |
| Notes | Comment |
| Billable status | Billable |
User Mapping
Automatic Matching
Users are matched by email:
- Core user email matches Everhour email
- Automatic linking occurs
- Time entries route correctly
Manual Mapping
If emails differ:
- Go to User Mapping
- Select Core team member
- Choose Everhour team member
- Save mapping
Unmapped Users
For time from unmapped users:
- Skip: Don't sync the entry
- Default user: Assign to specified user
- Queue: Hold for manual assignment
Time Entry Sync
From Core to Everhour
When time is logged in Core:
- Entry is created in Core
- Mapped project is identified
- Entry syncs to Everhour task
- Duration, notes, and billable status transfer
From Everhour to Core
When time is logged in Everhour:
- Entry is created in Everhour
- Linked Core ticket is identified
- Entry appears in Core
- User and details are mapped
Conflict Handling
When entries exist in both systems:
- Match by timestamp: Avoid duplicates
- Prefer source: Choose which system is authoritative
- Manual review: Flag conflicts for review
Task Mapping
Ticket-to-Task Linking
Link Core tickets to Everhour tasks:
Automatic: Based on title matching or project rules Manual: Link from ticket or Everhour
Creating Tasks
When syncing creates new Everhour tasks:
- Task is created in mapped project
- Title matches ticket title
- Description includes ticket details
- Link is stored for future sync
Billable Status
Sync Billable Flag
Billable status syncs:
- Core billable → Everhour billable
- Maintains accuracy for billing
Rate Handling
Hourly rates:
- Set in Everhour by project or user
- Core syncs time, Everhour calculates amounts
- Reports pull from Everhour for billing
Reports
Combined Reporting
Use both platforms' reports:
- Core: Operational reports, ticket-focused
- Everhour: Financial reports, invoice generation
Data Consistency
Ensure reports match:
- Verify sync is current
- Check for sync errors
- Reconcile discrepancies
- Use one platform as source of truth
Core now applies stricter completion checks so successful sync outcomes stay aligned with the entry status shown in Time Entries.
Troubleshooting
Time Not Syncing
Check:
- API key is valid (test connection)
- User is mapped correctly
- Project mapping exists
- Entry meets sync criteria
Duplicate Entries
Prevent duplicates:
- Set clear sync direction
- Don't log time in both systems
- Check sync logs for issues
Missing Time
If entries are missing:
- Check sync direction setting
- Verify user mapping
- Review sync rules
- Check Everhour API limits
Sync Errors
View error details:
- Go to integration settings
- Click Sync Logs
- Filter by status = Error
- Review error messages
Rate Limits
If hitting API limits:
- Reduce sync frequency
- Batch sync during off-hours
- Contact Everhour support
Best Practices
- Choose one system for entry: Avoid confusion
- Sync frequently: Keep data current
- Map all users: Prevent orphaned entries
- Monitor sync health: Check logs regularly
- Reconcile monthly: Verify data matches