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

1. Log in to Everhour
2. Go to Settings > Integrations
3. Find or generate your API key
4. Copy the key

Connecting to Core

1. Go to Settings > Integrations > Everhour
2. Click Connect
3. Paste your Everhour API key
4. Click Test Connection
5. If successful, click Save

Project Mapping

Choose which Everhour clients and projects sync into Core:

1. Open the Everhour sync filters.
2. Select a client to sync all its current and future projects.
3. Optionally include standalone projects outside the selected clients.
4. Mark private or internal projects as Never sync.
5. Save the filters.

Projects covered by a selected client are labeled Synced via client. Never-sync rules override both client and standalone-project selections.

Sync Configuration

Sync Direction

Choose data flow direction:

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

User Mapping

Automatic Matching

Users are matched by email:

1. Core user email matches Everhour email
2. Automatic linking occurs
3. Time entries route correctly

Manual Mapping

If emails differ:

1. Go to User Mapping
2. Select Core team member
3. Choose Everhour team member
4. 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:

1. Entry is created in Core
2. Mapped project is identified
3. Entry syncs to Everhour task
4. Duration, notes, and billable status transfer

From Everhour to Core

When time is logged in Everhour:

1. Entry is created in Everhour
2. Linked Core ticket is identified
3. Entry appears in Core
4. 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:

1. Task is created in mapped project
2. Title matches ticket title
3. Description includes ticket details
4. 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:

1. Verify sync is current
2. Check for sync errors
3. Reconcile discrepancies
4. 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:

1. API key is valid (test connection)
2. User is mapped correctly
3. Project mapping exists
4. Entry meets sync criteria

Duplicate Entries

Prevent duplicates:

1. Set clear sync direction
2. Don't log time in both systems
3. Check sync logs for issues

Duplicate Companies

When sync brings in an EverHour client, Core matches it against your existing companies before creating anything:

1. An exact name match is linked automatically — no duplicate is created.
2. A close match (similar name) is held in the Integration reconciliation queue (Settings → Integrations → Reconciliation) so you can either link it to the existing company or confirm it as new.
3. A genuinely new client is added as a new company.

If a client isn't syncing its projects yet, check the reconciliation queue — it may be waiting for you to confirm the company.

Missing Time

If entries are missing:

1. Check sync direction setting
2. Verify user mapping
3. Review sync rules
4. Check Everhour API limits

Sync Errors

View error details:

1. Go to integration settings
2. Click Sync Logs
3. Filter by status = Error
4. Review error messages

Rate Limits

If hitting API limits:

1. Reduce sync frequency
2. Batch sync during off-hours
3. 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

See also

• Integrations Overview
• Time Tracking
• Reports

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

1. Log in to Everhour
2. Go to Settings > Integrations
3. Find or generate your API key
4. Copy the key

Connecting to Core

1. Go to Settings > Integrations > Everhour
2. Click Connect
3. Paste your Everhour API key
4. Click Test Connection
5. If successful, click Save

Project Mapping

Choose which Everhour clients and projects sync into Core:

1. Open the Everhour sync filters.
2. Select a client to sync all its current and future projects.
3. Optionally include standalone projects outside the selected clients.
4. Mark private or internal projects as Never sync.
5. Save the filters.

Projects covered by a selected client are labeled Synced via client. Never-sync rules override both client and standalone-project selections.

Sync Configuration

Sync Direction

Choose data flow direction:

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

User Mapping

Automatic Matching

Users are matched by email:

1. Core user email matches Everhour email
2. Automatic linking occurs
3. Time entries route correctly

Manual Mapping

If emails differ:

1. Go to User Mapping
2. Select Core team member
3. Choose Everhour team member
4. 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:

1. Entry is created in Core
2. Mapped project is identified
3. Entry syncs to Everhour task
4. Duration, notes, and billable status transfer

From Everhour to Core

When time is logged in Everhour:

1. Entry is created in Everhour
2. Linked Core ticket is identified
3. Entry appears in Core
4. 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:

1. Task is created in mapped project
2. Title matches ticket title
3. Description includes ticket details
4. 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:

1. Verify sync is current
2. Check for sync errors
3. Reconcile discrepancies
4. 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:

1. API key is valid (test connection)
2. User is mapped correctly
3. Project mapping exists
4. Entry meets sync criteria

Duplicate Entries

Prevent duplicates:

1. Set clear sync direction
2. Don't log time in both systems
3. Check sync logs for issues

Duplicate Companies

When sync brings in an EverHour client, Core matches it against your existing companies before creating anything:

1. An exact name match is linked automatically — no duplicate is created.
2. A close match (similar name) is held in the Integration reconciliation queue (Settings → Integrations → Reconciliation) so you can either link it to the existing company or confirm it as new.
3. A genuinely new client is added as a new company.

If a client isn't syncing its projects yet, check the reconciliation queue — it may be waiting for you to confirm the company.

Missing Time

If entries are missing:

1. Check sync direction setting
2. Verify user mapping
3. Review sync rules
4. Check Everhour API limits

Sync Errors

View error details:

1. Go to integration settings
2. Click Sync Logs
3. Filter by status = Error
4. Review error messages

Rate Limits

If hitting API limits:

1. Reduce sync frequency
2. Batch sync during off-hours
3. 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

See also

• Integrations Overview
• Time Tracking
• Reports