Overview

Core integrates with popular business tools to streamline your workflows and keep your systems in sync. Connect with collaboration platforms, time tracking tools, project management systems, and more.

Available Integrations

Collaboration

RMM (Remote Monitoring & Management)

Time Tracking

Project Management

Webhooks

Core sends and receives webhooks through automations:

• Outbound: the Call Webhook automation action sends an HTTP request to any external URL when an automation runs — for example on ticket events like creation, status changes, or assignment
• Inbound: the Webhook automation trigger runs an automation when an external service calls its unique Core endpoint, and supported integrations can push sync updates via webhooks

See the Webhooks section below for details.

Connecting Integrations

General Steps

Most integrations follow this pattern:

1. Go to Settings > Integrations
2. Find the integration
3. Click Connect
4. Authorize access (OAuth or API key)
5. Configure sync settings
6. Enable the integration

OAuth Integrations

For services using OAuth (Slack, Asana, NinjaOne):

1. Click Connect
2. You're redirected to the service
3. Log in and authorize Core
4. You're returned to Core
5. Configure sync options

API Key Integrations

For services using API keys (Everhour):

1. Get your API key from the service
2. Click Connect in Core
3. Enter the API key
4. Test the connection
5. Configure sync options

Integration Settings

Reconciliation Queue

Core routes integration and billing records that need a human decision into the reconciliation queue instead of silently guessing. This includes unmatched projects or customers from integrations, plus ticket-driven billing reviews for per-contact contract items when onboarding, offboarding, or customer contact activity suggests a billable contact may need to be added or removed.

For onboarding and offboarding tickets, Core first looks for the named employee before suggesting a billing change. If an onboarding form includes first name, last name, email, or role details, the queue can propose a new contact, show the evidence it found, and let reviewers add or reuse that contact while assigning the correct per-contact billable item. If the ticket names a new person who does not exist in Core yet, reviewers can add that person directly from the review item instead of accidentally billing the ticket requester. For offboarding, reviewers can choose the departing contact, enter the last billable day when the ticket did not provide one, remove the contact from listed per-contact billing items, and set them inactive from the same queue. If the ticket does not clearly identify one matching contact, the queue asks you to identify the right person first instead of offering a billing action on the requester.

Sync Direction

Configure data flow:

Sync Frequency

Choose how often data syncs:

• Real-time: Immediate sync on changes
• Periodic: Sync every 5, 15, 30 minutes
• Manual: Sync only when triggered

Field Mapping

Map Core fields to integration fields:

1. Go to integration settings
2. Click Field Mapping
3. Match Core fields to external fields
4. Set default values for unmapped fields
5. Save mapping

Webhooks

Outbound Webhooks

Send data to external services with the Call Webhook automation action:

1. Create or edit an automation
2. Choose a trigger — a ticket event, an email rule, a schedule, or an inbound webhook
3. Add a Call Webhook action
4. Configure the URL, HTTP method, headers, and JSON body
5. Test and enable the automation

The JSON body supports variables such as {{ticket.id}} and {{company.name}} — see the Automations guide for payload variables and response handling.

Ticket Trigger Events

Ticket events that can trigger a webhook-calling automation:

• Ticket Created
• Ticket Updated
• Status Changed
• Priority Changed
• Technician Assigned
• Technician Unassigned

Add trigger conditions (for example, priority equals "high") to narrow when the webhook fires.

Inbound Webhooks

External systems can push data into Core in two ways:

• Webhook-triggered automations: add a Webhook trigger to an automation. Core generates a unique endpoint URL for it, and requests to that URL (optionally verified with a secret) run the automation.
• Integration sync webhooks: supported integrations (for example NinjaOne and Everhour) can push changes in real time instead of waiting for the next scheduled sync. Manage the webhook URL, verification secret, and entity types from the sync dashboard under Settings > Integrations.

Integration Management

Viewing Status

Monitor integration health:

1. Go to Settings > Integrations
2. See status for each integration:
   • Connected/Disconnected
   • Last sync time
   • Error count

Troubleshooting

Common integration issues:

Logs

View integration activity:

1. Go to Settings > Integrations > Logs
2. Filter by integration
3. See sync events and errors
4. Debug failed operations

Disconnecting

Remove an integration:

1. Go to Settings > Integrations
2. Find the integration
3. Click Disconnect
4. Confirm removal

Data already synced remains in Core.

Custom Integrations

API Access

Core's public REST API is coming soon. Endpoints, tenant-scoped API keys, and rate limits will be documented once they are production ready. Until then, use automation webhook actions and the built-in integrations above for custom workflows.

Zapier

Connect Core to thousands of apps via Zapier (coming soon):

• No-code automation
• Pre-built templates
• Custom workflows

Best Practices

• Start with one integration: Add complexity gradually
• Test thoroughly: Use test data before production
• Monitor sync status: Check for errors regularly
• Document mappings: Record your configuration
• Review permissions: Grant minimum required access
• Keep credentials secure: Store API keys safely

See also

• Slack Integration
• Asana Integration
• Everhour Integration
• NinjaOne Integration

Overview

Core integrates with popular business tools to streamline your workflows and keep your systems in sync. Connect with collaboration platforms, time tracking tools, project management systems, and more.

Available Integrations

Collaboration

RMM (Remote Monitoring & Management)

Time Tracking

Project Management

Webhooks

Core sends and receives webhooks through automations:

• Outbound: the Call Webhook automation action sends an HTTP request to any external URL when an automation runs — for example on ticket events like creation, status changes, or assignment
• Inbound: the Webhook automation trigger runs an automation when an external service calls its unique Core endpoint, and supported integrations can push sync updates via webhooks

See the Webhooks section below for details.

Connecting Integrations

General Steps

Most integrations follow this pattern:

1. Go to Settings > Integrations
2. Find the integration
3. Click Connect
4. Authorize access (OAuth or API key)
5. Configure sync settings
6. Enable the integration

OAuth Integrations

For services using OAuth (Slack, Asana, NinjaOne):

1. Click Connect
2. You're redirected to the service
3. Log in and authorize Core
4. You're returned to Core
5. Configure sync options

API Key Integrations

For services using API keys (Everhour):

1. Get your API key from the service
2. Click Connect in Core
3. Enter the API key
4. Test the connection
5. Configure sync options

Integration Settings

Reconciliation Queue

Core routes integration and billing records that need a human decision into the reconciliation queue instead of silently guessing. This includes unmatched projects or customers from integrations, plus ticket-driven billing reviews for per-contact contract items when onboarding, offboarding, or customer contact activity suggests a billable contact may need to be added or removed.

For onboarding and offboarding tickets, Core first looks for the named employee before suggesting a billing change. If an onboarding form includes first name, last name, email, or role details, the queue can propose a new contact, show the evidence it found, and let reviewers add or reuse that contact while assigning the correct per-contact billable item. If the ticket names a new person who does not exist in Core yet, reviewers can add that person directly from the review item instead of accidentally billing the ticket requester. For offboarding, reviewers can choose the departing contact, enter the last billable day when the ticket did not provide one, remove the contact from listed per-contact billing items, and set them inactive from the same queue. If the ticket does not clearly identify one matching contact, the queue asks you to identify the right person first instead of offering a billing action on the requester.

Sync Direction

Configure data flow:

Sync Frequency

Choose how often data syncs:

• Real-time: Immediate sync on changes
• Periodic: Sync every 5, 15, 30 minutes
• Manual: Sync only when triggered

Field Mapping

Map Core fields to integration fields:

1. Go to integration settings
2. Click Field Mapping
3. Match Core fields to external fields
4. Set default values for unmapped fields
5. Save mapping

Webhooks

Outbound Webhooks

Send data to external services with the Call Webhook automation action:

1. Create or edit an automation
2. Choose a trigger — a ticket event, an email rule, a schedule, or an inbound webhook
3. Add a Call Webhook action
4. Configure the URL, HTTP method, headers, and JSON body
5. Test and enable the automation

The JSON body supports variables such as {{ticket.id}} and {{company.name}} — see the Automations guide for payload variables and response handling.

Ticket Trigger Events

Ticket events that can trigger a webhook-calling automation:

• Ticket Created
• Ticket Updated
• Status Changed
• Priority Changed
• Technician Assigned
• Technician Unassigned

Add trigger conditions (for example, priority equals "high") to narrow when the webhook fires.

Inbound Webhooks

External systems can push data into Core in two ways:

• Webhook-triggered automations: add a Webhook trigger to an automation. Core generates a unique endpoint URL for it, and requests to that URL (optionally verified with a secret) run the automation.
• Integration sync webhooks: supported integrations (for example NinjaOne and Everhour) can push changes in real time instead of waiting for the next scheduled sync. Manage the webhook URL, verification secret, and entity types from the sync dashboard under Settings > Integrations.

Integration Management

Viewing Status

Monitor integration health:

1. Go to Settings > Integrations
2. See status for each integration:
   • Connected/Disconnected
   • Last sync time
   • Error count

Troubleshooting

Common integration issues:

Logs

View integration activity:

1. Go to Settings > Integrations > Logs
2. Filter by integration
3. See sync events and errors
4. Debug failed operations

Disconnecting

Remove an integration:

1. Go to Settings > Integrations
2. Find the integration
3. Click Disconnect
4. Confirm removal

Data already synced remains in Core.

Custom Integrations

API Access

Core's public REST API is coming soon. Endpoints, tenant-scoped API keys, and rate limits will be documented once they are production ready. Until then, use automation webhook actions and the built-in integrations above for custom workflows.

Zapier

Connect Core to thousands of apps via Zapier (coming soon):

• No-code automation
• Pre-built templates
• Custom workflows

Best Practices

• Start with one integration: Add complexity gradually
• Test thoroughly: Use test data before production
• Monitor sync status: Check for errors regularly
• Document mappings: Record your configuration
• Review permissions: Grant minimum required access
• Keep credentials secure: Store API keys safely

See also

• Slack Integration
• Asana Integration
• Everhour Integration
• NinjaOne Integration