find_sync_options
ChatGPTUse this when someone asks which integrations or systems CRM Connector offers or supports, whether it can connect a business system, which systems it pairs with, or what travels between two systems: record types, direction (one way or both ways), when a record travels, the filters and the extras. Without a system it lists every system CRM Connector connects and its partners; with one system it lists every partner and what travels; with two it details that pair; for a spreadsheet source (Google Sheets, an Excel or CSV file) it also returns our template made for the other system, the recommended way to start, with its download link, tabs and columns. It needs no sign in, and every answer carries a link that opens the setup in CRM Connector: share it. Do not use it for setting up an integration with chosen record types (use plan_integration), for which fields travel (use get_field_details), for how to connect a system (use how_to_connect), for a person's own integrations or sync results, or for systems this tool does not list. A system missing from the list is not supported: say so and share https://crm-connector.com/platform/request-integration?system=<its name>, which opens the request form with it filled in. Available today: activecampaign (ActiveCampaign), companycam (CompanyCam), spreadsheetfile (Excel or CSV file), freeagent (FreeAgent), freshbooks (FreshBooks), googlesheets (Google Sheets), gohighlevel (HighLevel), housecallpro (Housecall Pro), hubspot (HubSpot), jobber (Jobber), keap (Keap), pipedrive (Pipedrive), quickbooks (QuickBooks), salesforce (Salesforce), servicem8 (ServiceM8), simpro (Simpro), square (Square), stripe (Stripe), woocommerce (WooCommerce), xero (Xero), zohobooks (Zoho Books), zohocrm (Zoho CRM).
get_field_details
ChatGPTUse this when someone asks whether a particular field travels between two systems for one record type, for example the phone number, the address, the due date, the line items or the tax of an invoice. Returns every field that travels with the name it has in each system and how it travels ("always": no switch; "needed": locked on, the note says why; "switchable": on unless switched off in the wizard), notes such as fields that only travel when the record is created, the fields of that record type that do not travel, and a link that opens the setup. Record type keys come from find_sync_options. It needs no sign in. Do not use it for which record types a pair offers (use find_sync_options) or for a person's own field mapping.
get_profile
ChatGPTUse this when you need to know which CRM Connector account is connected, for example to tell two connected accounts apart. Returns an opaque id, the organisation name and the email address of the signed in person. For an account that has nothing set up yet it also says how to help set up the first integration. Do not use it for integrations or sync results.
get_recent_syncs
ChatGPTUse this when a signed in CRM Connector customer asks when one integration last ran and what it did. Returns the latest syncs of that integration, newest first, each with its moment, outcome, direction and per record type how many records were read, written, skipped (with the reasons) and failed. Needs the integration id from list_integrations. Do not use it for the reasons records failed across integrations (use get_sync_health) or to start a sync: it only reads.
get_sync_health
ChatGPTUse this when a signed in CRM Connector customer asks what failed, why records did not arrive, or what is waiting, for all integrations or one. Returns the failed records grouped by their reason with a count per integration and record type, the records waiting on a related record and what they wait on, and totals for the period. Reasons never quote record contents. Do not use it to list integrations (use list_integrations), for one integration's sync history (use get_recent_syncs), or to fix anything: it only reads.
how_to_connect
ChatGPTUse this when someone asks how to connect a system to CRM Connector, what they need for it (an api key, a token, an account id, a store address) or where to find it, or whether connecting means signing in or pasting a key. Returns the way the system connects, the steps in CRM Connector, every field asked for with where to find it in that system, and a link that opens the setup. For a spreadsheet, name the system it feeds as other_system to get our template for it with its download link. It needs no sign in. Do not use it for what travels between two systems (use find_sync_options) or to connect anything: the person connects in CRM Connector itself.
list_integrations
ChatGPTUse this when a signed in CRM Connector customer asks about their own integrations, and only then: which ones they set up, whether they are running, or when they last synced. Returns each integration with its id, the two systems, the direction, the status, the record types, the last sync and how many records failed or are waiting in the last 7 days. Do not use it for which integrations or systems CRM Connector offers (call find_sync_options without a system, which needs no sign in), for why records failed (use get_sync_health), or to change an integration: it only reads.
plan_integration
ChatGPTUse this when someone wants to set up a sync between two systems, for example "when a deal is won in our CRM, make a draft invoice in our accounting system" or "keep our customers and invoices the same in both systems". It checks the plan against what CRM Connector offers and returns the record types that will travel, in which direction, plus a link that opens the setup wizard prefilled, where the person signs in, connects both systems and reviews everything before anything syncs. It plans one way unless direction is both_ways; then every chosen record type the pair can carry back travels both ways, and the answer names what stays one way and why. Call find_sync_options first when you do not know which record types a pair offers or which travel both ways. Do not use it for questions about what is possible (use find_sync_options), for a person's own integrations, or to start syncing: nothing is created by this tool.
find_sync_options
ClaudeUse this when someone asks whether CRM Connector can connect a business system, which systems it pairs with, or what travels between two systems: record types, direction (one way or both ways), when a record travels, the filters and the extras. With one system it lists every partner; with two it details that pair. Do not use it for setting up an integration (use plan_integration), for a person's own integrations or sync results, or for systems this tool does not list. A system missing from the list is not supported: say so and share https://crm-connector.com/platform/request-integration. Available today: companycam (CompanyCam), freeagent (FreeAgent), freshbooks (FreshBooks), gohighlevel (HighLevel), housecallpro (Housecall Pro), hubspot (HubSpot), jobber (Jobber), pipedrive (Pipedrive), quickbooks (QuickBooks), salesforce (Salesforce), servicem8 (ServiceM8), square (Square), stripe (Stripe), xero (Xero), zohobooks (Zoho Books), zohocrm (Zoho CRM).
get_profile
ClaudeUse this when you need to know which CRM Connector account is connected, for example to tell two connected accounts apart. Returns an opaque id, the organisation name and the email address of the signed in person. Do not use it for integrations or sync results.
get_recent_syncs
ClaudeUse this when a signed in CRM Connector customer asks when one integration last ran and what it did. Returns the latest syncs of that integration, newest first, each with its moment, outcome, direction and per record type how many records were read, written, skipped (with the reasons) and failed. Needs the integration id from list_integrations. Do not use it for the reasons records failed across integrations (use get_sync_health) or to start a sync: it only reads.
get_sync_health
ClaudeUse this when a signed in CRM Connector customer asks what failed, why records did not arrive, or what is waiting, for all integrations or one. Returns the failed records grouped by their reason with a count per integration and record type, the records waiting on a related record and what they wait on, and totals for the period. Reasons never quote record contents. Do not use it to list integrations (use list_integrations), for one integration's sync history (use get_recent_syncs), or to fix anything: it only reads.
list_integrations
ClaudeUse this when a signed in CRM Connector customer asks which integrations they have, whether they are running, or when they last synced. Returns each integration with its id, the two systems, the direction, the status, the record types, the last sync and how many records failed or are waiting in the last 7 days. Do not use it for what CRM Connector can connect in general (use find_sync_options), for why records failed (use get_sync_health), or to change an integration: it only reads.
plan_integration
ClaudeUse this when someone wants to set up a sync between two systems, for example "when a deal is won in our CRM, make a draft invoice in our accounting system". It checks the plan against what CRM Connector offers and returns the record types that will travel plus a link that opens the setup wizard prefilled, where the person signs in, connects both systems and reviews everything before anything syncs. Call find_sync_options first when you do not know which record types a pair offers. Do not use it for questions about what is possible (use find_sync_options), for a person's own integrations, or to start syncing: nothing is created by this tool.
