Everything you need to get syncing

1. 1.Go to the HubSpot App Marketplace and search for "300Sync" or the name of your specific integration (e.g., "300Sync for Clio").
2. 2.Click Install app. You will be prompted to select which HubSpot portal to install it into if you manage multiple portals.
3. 3.Review the list of requested OAuth scopes — these are the permissions 300Sync needs to read and write CRM data on your behalf. Click Connect app to authorize.
4. 4.After authorization, HubSpot will redirect you to the 300Sync onboarding wizard inside HubSpot. The integration is now installed.

1. 1.In HubSpot, navigate to any Contact, Company, or Deal record. You will see a 300Sync panel in the right sidebar.
2. 2.Click the settings gear icon or open the integration's dedicated settings tab (labeled with the integration name, e.g., "Clio Settings").
3. 3.Click Connect and follow the OAuth authorization flow in the pop-up window. Log in to your integration account and grant access when prompted.
4. 4.Once authorized, the settings panel will show your connected account name and a green status indicator. You're connected.

After connecting, you can configure which object types sync, how frequently, and what happens when a conflict occurs.

300Sync includes sensible default field mappings for every integration. You can customize these at any time without re-authorizing.

• Default mappings cover the most commonly used fields and are active immediately after setup.
• Add custom mappings to route any integration field to any standard or custom HubSpot property.
• Nested fields are supported using dot notation (e.g.,address.city).
• Changes to field mappings take effect on the next scheduled sync. Trigger a manual sync to apply immediately.

300Sync for Clio syncs 4 object types with 27 default field mappings across them.

Clio matter status maps directly to HubSpot deal stages. The mapping is automatic and does not require configuration.

Practice area is stored as a custom HubSpot property (sync300_clio_practice_area) on the Deal record.

300Sync automatically creates HubSpot associations that mirror the relationships in Clio. You don't need to configure this manually.

• Clio Contacts linked to a Matter are associated as HubSpot Contact → Deal.
• Clio Companies are associated with their related Contacts in HubSpot.
• Clio Tasks on a Matter are associated as HubSpot Ticket → Deal.
• Contacts and Companies sync first, then Matters and Tasks, ensuring all associations resolve correctly.

By default, 300Sync for Clio is one-way: Clio data flows into HubSpot. Bidirectional sync can be enabled per-object type in settings, allowing changes made in HubSpot to be written back to Clio.

A conflict occurs when the same field has been updated in both systems since the last sync. Choose which value takes precedence.

You can trigger a sync at any time without waiting for the scheduled interval.

• From the CRM sidebar card: Click the "Sync now" button on any Contact, Company, Deal, or Ticket record.
• From a workflow action: Use the "Trigger Sync" workflow action to kick off a full sync as part of any automation.
• From the 300Sync dashboard: View sync history, see which runs succeeded or failed, and examine per-object record counts.

The record tab card appears as a dedicated tab on the Contact, Company, Deal, and Ticket record pages. It provides a full-detail view of the synced record.

• All synced field values from the integration, side by side with HubSpot property names.
• Last sync timestamp and sync run status (success / error).
• A "View in Clio" deep link that opens the record directly in your integration software.
• Available on: Contacts, Companies, Deals, and Tickets.

The sidebar card appears in the right panel of every HubSpot record. It gives an at-a-glance sync status without navigating away.

• Sync status indicator: synced, not synced, or error.
• Last sync time (relative, e.g., "3 minutes ago").
• "Sync now" button to trigger an immediate manual sync.
• Available on: Contacts, Companies, Deals, and Tickets.

Manually trigger a full sync from any HubSpot workflow or Breeze AI agent. Useful for ensuring data is current before a follow-up action runs.

Create a new contact record in Clio from HubSpot data. The contact is automatically linked to the HubSpot record via the sync ID.

Create a new Clio matter and associate it with an existing Clio client. Requires the Clio Contact ID, available on the HubSpot contact record after initial sync.

Create a Clio task linked to a matter. Automatically assigns to the matter's responsible attorney if no assignee is specified.

Change a Clio matter's status directly from a HubSpot workflow. Useful for automating status transitions when a deal stage changes.

Log a note or activity entry on a Clio contact or matter. The note text can include HubSpot property tokens for dynamic content.

• All integrations use OAuth 2.0. No usernames or passwords are ever stored.
• OAuth access tokens and refresh tokens are encrypted at rest using AES-256-GCM before being written to the database.
• For credential-based integrations (not OAuth), credentials are also encrypted with AES-256-GCM and never logged.
• OAuth state parameters use a session-bound nonce with a 10-minute expiry to prevent CSRF attacks.
• Tokens are automatically refreshed before they expire — no user action required.

• All requests from HubSpot UI Extensions are verified using HMAC v3 signature verification before any data is returned.
• CORS is restricted to allowlisted HubSpot domains (app.hubspot.com and regional variants).
• Security headers applied on all responses: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Content-Security-Policy.
• No PII (email, phone, name, tokens) is ever written to application logs.

• 300Sync is a pass-through sync engine. Synced record data is not stored in our database — it is transformed and passed directly to the destination.
• Only sync metadata is stored: connection IDs, timestamps, record counts, and error messages.
• Healthcare integrations (Open Dental, Boulevard) apply a HIPAA data classification filter — clinical notes, medical history, and treatment details are never synced to HubSpot.
• SOC 2 Type II principles are followed in our development and operations practices.