Update to CRM Connector
Snapshot Oct 31, 2026 · 15:03 UTC · version 1.1.2
Collection source: downloaded plugin package.
Instructions updated for explore-integrations
Skill instructions — Now says: - "How do I connect Xero?", "What do I need for GoHighLevel?", "Where do I find my token?" - Call `get_connection_guide` with the system.
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 10 plugins free · no card required.
All fields and original values.
Skill instructions
Oct 28, 2026 · 12:50 UTC
- "How do I connect Xero?", "What do I need for HighLevel?", "Where do I find my token?" - Call `how_to_connect` with the system.
Oct 31, 2026 · 15:03 UTC
- "How do I connect Xero?", "What do I need for GoHighLevel?", "Where do I find my token?" - Call `get_connection_guide` with the system.
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -35,8 +35,8 @@ ## How to connect a system -- "How do I connect Xero?", "What do I need for HighLevel?", "Where do I find my token?" -- Call `how_to_connect` with the system. +- "How do I connect Xero?", "What do I need for GoHighLevel?", "Where do I find my token?" +- Call `get_connection_guide` with the system. - Give the steps in CRM Connector and, for each field it asks for, where to find it in that system. ## Next step
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: explore-integrations\ndescription: Answer questions about what CRM Connector connects before anything is set up. Use it when a person asks which systems CRM Connector supports, what two systems can sync, whether a particular field goes across, or how to connect a system.\n---\n\n# Explore what CRM Connector connects\n\nThis belongs to part 1 of the plugin, **Integrations between two systems**. None of these questions needs a CRM Connector account. Answer from the tools, then offer the next step.\n\n## Which systems CRM Connector connects\n\n- \"Which integrations do you have?\", \"What can CRM Connector connect?\", \"Do you support Keap?\"\n- Call `find_sync_options` without a system. It names the plugin's two products and lists every system with the systems it pairs with.\n- Name both products, kept apart: integrations between two systems (from that list), and AI Agents inside one system (reading, changing and automating its records, set up per system on request). Then offer to show what travels between two of them.\n- Do not call `list_integrations` for this: that tool is only about the integrations a customer has set up.\n\n## What two systems can sync\n\n- \"Can I sync Pipedrive with Xero?\", \"What goes across between HubSpot and QuickBooks Online?\"\n- Call `find_sync_options` with both systems.\n- Say per record type:\n - in which direction it travels, one way or both ways\n - at which moment a record can travel, for example once an invoice is paid or a quote is accepted\n - which filters apply, for example tags, pipeline stages or a minimum amount\n\n## Whether a field goes across\n\n- \"Does the phone number go across?\", \"Is the due date carried?\", \"Do the line items come along?\"\n- Call `get_field_details` with the two systems and the record type key.\n- Say plainly whether that field travels and how:\n - **always**: it always goes across\n - **needed**: the sync needs it, so it cannot be switched off\n - **switchable**: the person can switch it off in the setup\n- Pass on notes such as \"only when the record is created\" and name what does not travel.\n\n## How to connect a system\n\n- \"How do I connect Xero?\", \"What do I need for HighLevel?\", \"Where do I find my token?\"\n- Call `how_to_connect` with the system.\n- Give the steps in CRM Connector and, for each field it asks for, where to find it in that system.\n\n## Next step\n\n- Every answer from these tools carries a setup link: share it, so the person can start right away.\n- When they describe what should happen, for example \"when a deal is won, make an invoice\", continue with the set-up-a-sync skill and make a plan.\n- When a system or combination is not offered, say so and share the request an integration link the tool gives.\n\n## Rules\n\n- Only describe what the tools return. Never promise a record type, direction, field or system the tools did not confirm.\n- Do not discuss prices, plans, trials or discounts.\n- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.\n"
"---\nname: explore-integrations\ndescription: Answer questions about what CRM Connector connects before anything is set up. Use it when a person asks which systems CRM Connector supports, what two systems can sync, whether a particular field goes across, or how to connect a system.\n---\n\n# Explore what CRM Connector connects\n\nThis belongs to part 1 of the plugin, **Integrations between two systems**. None of these questions needs a CRM Connector account. Answer from the tools, then offer the next step.\n\n## Which systems CRM Connector connects\n\n- \"Which integrations do you have?\", \"What can CRM Connector connect?\", \"Do you support Keap?\"\n- Call `find_sync_options` without a system. It names the plugin's two products and lists every system with the systems it pairs with.\n- Name both products, kept apart: integrations between two systems (from that list), and AI Agents inside one system (reading, changing and automating its records, set up per system on request). Then offer to show what travels between two of them.\n- Do not call `list_integrations` for this: that tool is only about the integrations a customer has set up.\n\n## What two systems can sync\n\n- \"Can I sync Pipedrive with Xero?\", \"What goes across between HubSpot and QuickBooks Online?\"\n- Call `find_sync_options` with both systems.\n- Say per record type:\n - in which direction it travels, one way or both ways\n - at which moment a record can travel, for example once an invoice is paid or a quote is accepted\n - which filters apply, for example tags, pipeline stages or a minimum amount\n\n## Whether a field goes across\n\n- \"Does the phone number go across?\", \"Is the due date carried?\", \"Do the line items come along?\"\n- Call `get_field_details` with the two systems and the record type key.\n- Say plainly whether that field travels and how:\n - **always**: it always goes across\n - **needed**: the sync needs it, so it cannot be switched off\n - **switchable**: the person can switch it off in the setup\n- Pass on notes such as \"only when the record is created\" and name what does not travel.\n\n## How to connect a system\n\n- \"How do I connect Xero?\", \"What do I need for GoHighLevel?\", \"Where do I find my token?\"\n- Call `get_connection_guide` with the system.\n- Give the steps in CRM Connector and, for each field it asks for, where to find it in that system.\n\n## Next step\n\n- Every answer from these tools carries a setup link: share it, so the person can start right away.\n- When they describe what should happen, for example \"when a deal is won, make an invoice\", continue with the set-up-a-sync skill and make a plan.\n- When a system or combination is not offered, say so and share the request an integration link the tool gives.\n\n## Rules\n\n- Only describe what the tools return. Never promise a record type, direction, field or system the tools did not confirm.\n- Do not discuss prices, plans, trials or discounts.\n- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.\n"
Full snapshot data
{
"description": "Answer questions about what CRM Connector connects before anything is set up. Use it when a person asks which systems CRM Connector supports, what two systems can sync, whether a particular field goes across, or how to connect a system.",
"included_files": [],
"name": "explore-integrations",
"skill_md_contents": "---\nname: explore-integrations\ndescription: Answer questions about what CRM Connector connects before anything is set up. Use it when a person asks which systems CRM Connector supports, what two systems can sync, whether a particular field goes across, or how to connect a system.\n---\n\n# Explore what CRM Connector connects\n\nThis belongs to part 1 of the plugin, **Integrations between two systems**. None of these questions needs a CRM Connector account. Answer from the tools, then offer the next step.\n\n## Which systems CRM Connector connects\n\n- \"Which integrations do you have?\", \"What can CRM Connector connect?\", \"Do you support Keap?\"\n- Call `find_sync_options` without a system. It names the plugin's two products and lists every system with the systems it pairs with.\n- Name both products, kept apart: integrations between two systems (from that list), and AI Agents inside one system (reading, changing and automating its records, set up per system on request). Then offer to show what travels between two of them.\n- Do not call `list_integrations` for this: that tool is only about the integrations a customer has set up.\n\n## What two systems can sync\n\n- \"Can I sync Pipedrive with Xero?\", \"What goes across between HubSpot and QuickBooks Online?\"\n- Call `find_sync_options` with both systems.\n- Say per record type:\n - in which direction it travels, one way or both ways\n - at which moment a record can travel, for example once an invoice is paid or a quote is accepted\n - which filters apply, for example tags, pipeline stages or a minimum amount\n\n## Whether a field goes across\n\n- \"Does the phone number go across?\", \"Is the due date carried?\", \"Do the line items come along?\"\n- Call `get_field_details` with the two systems and the record type key.\n- Say plainly whether that field travels and how:\n - **always**: it always goes across\n - **needed**: the sync needs it, so it cannot be switched off\n - **switchable**: the person can switch it off in the setup\n- Pass on notes such as \"only when the record is created\" and name what does not travel.\n\n## How to connect a system\n\n- \"How do I connect Xero?\", \"What do I need for GoHighLevel?\", \"Where do I find my token?\"\n- Call `get_connection_guide` with the system.\n- Give the steps in CRM Connector and, for each field it asks for, where to find it in that system.\n\n## Next step\n\n- Every answer from these tools carries a setup link: share it, so the person can start right away.\n- When they describe what should happen, for example \"when a deal is won, make an invoice\", continue with the set-up-a-sync skill and make a plan.\n- When a system or combination is not offered, say so and share the request an integration link the tool gives.\n\n## Rules\n\n- Only describe what the tools return. Never promise a record type, direction, field or system the tools did not confirm.\n- Do not discuss prices, plans, trials or discounts.\n- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.\n"
}SHA-256 of public snapshot: 712267a3a51f66f61a21bf0d6a5b50a6f5f8daf794b4b717d1d6529e70a709d0