← CRM ConnectorCONTENT HISTORY

Update to CRM Connector

Snapshot Nov 6, 2026 · 00:12 UTC · version 1.4.1

Collection source: downloaded plugin package.

WHAT CHANGED

Instructions updated for explore-integrations

Skill instructions — Now says: --- name: explore-integrations description: Answer questions about what CRM Connector connects before anything is set up. Use it when a person asks which...

Observed in instructions or declared skills. Runtime behavior has not been tested.

Save CRM Connector and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

Nov 3, 2026 · 18:56 UTC

--- name: explore-integrations 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 f...

After

Nov 6, 2026 · 00:12 UTC

--- name: explore-integrations 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 fie...

Compare saved observations

Download comparison JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,52 +1,52 @@
----
-name: explore-integrations
-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.
----
-
-# Explore what CRM Connector connects
-
-This belongs to part 2 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.
-
-## Which systems CRM Connector connects
-
-- "Which integrations do you have?", "What can CRM Connector connect?", "Do you support Keap?"
-- Call `find_sync_options` without a system. It names the plugin's two products and lists every system with the systems it pairs with.
-- Name both products, kept apart: integrations between two systems (from that list), and AI Agents inside one system (reading, changing and automating its records; `get_ai_agents_info` lists the systems it works with; follow the `explore-ai-agents` skill for questions about it). Then offer to show what travels between two of them.
-- Do not call `list_integrations` for this: that tool is only about the integrations a customer has set up.
-
-## What two systems can sync
-
-- "Can I sync Pipedrive with Xero?", "What goes across between HubSpot and QuickBooks Online?"
-- Call `find_sync_options` with both systems.
-- Say per record type:
-  - in which direction it travels, one way or both ways
-  - at which moment a record can travel, for example once an invoice is paid or a quote is accepted
-  - which filters apply, for example tags, pipeline stages or a minimum amount
-
-## Whether a field goes across
-
-- "Does the phone number go across?", "Is the due date carried?", "Do the line items come along?"
-- Call `get_field_details` with the two systems and the record type key.
-- Say plainly whether that field travels and how:
-  - **always**: it always goes across
-  - **needed**: the sync needs it, so it cannot be switched off
-  - **switchable**: the person can switch it off in the setup
-- Pass on notes such as "only when the record is created" and name what does not travel.
-
-## How to connect a 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
-
-- Every answer from these tools carries a setup link: share it, so the person can start right away.
-- 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.
-- When a system or combination is not offered, say so and share the request an integration link the tool gives.
-
-## Rules
-
-- Only describe what the tools return. Never promise a record type, direction, field or system the tools did not confirm.
-- Do not discuss prices, plans, trials or discounts.
-- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.
+---
+name: explore-integrations
+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.
+---
+
+# Explore what CRM Connector connects
+
+This belongs to part 2 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.
+
+## Which systems CRM Connector connects
+
+- "Which integrations do you have?", "What can CRM Connector connect?", "Do you support Keap?"
+- Call `get_integration_options` without a system. It names the plugin's two products and lists every system with the systems it pairs with.
+- Name both products, kept apart: integrations between two systems (from that list), and AI Agents inside one system (reading, changing and automating its records; `get_ai_agent_options` lists the systems it works with; follow the `plan-an-ai-agent` skill for questions about it). Then offer to show what travels between two of them.
+- Do not call `list_integrations` for this: that tool is only about the integrations a customer has set up.
+
+## What two systems can sync
+
+- "Can I sync Pipedrive with Xero?", "What goes across between HubSpot and QuickBooks Online?"
+- Call `get_integration_options` with both systems.
+- Say per record type:
+  - in which direction it travels, one way or both ways
+  - at which moment a record can travel, for example once an invoice is paid or a quote is accepted
+  - which filters apply, for example tags, pipeline stages or a minimum amount
+
+## Whether a field goes across
+
+- "Does the phone number go across?", "Is the due date carried?", "Do the line items come along?"
+- Call `get_integration_fields` with the two systems and the record type key.
+- Say plainly whether that field travels and how:
+  - **always**: it always goes across
+  - **needed**: the sync needs it, so it cannot be switched off
+  - **switchable**: the person can switch it off in the setup
+- Pass on notes such as "only when the record is created" and name what does not travel.
+
+## How to connect a 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
+
+- Every answer from these tools carries a setup link: share it, so the person can start right away.
+- When they describe what should happen, for example "when a deal is won, make an invoice", continue with the plan-an-integration skill and make a plan.
+- When a system or combination is not offered, say so and share the request an integration link the tool gives.
+
+## Rules
+
+- Only describe what the tools return. Never promise a record type, direction, field or system the tools did not confirm.
+- Do not discuss prices, plans, trials or discounts.
+- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\r\nname: explore-integrations\r\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.\r\n---\r\n\r\n# Explore what CRM Connector connects\r\n\r\nThis belongs to part 2 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.\r\n\r\n## Which systems CRM Connector connects\r\n\r\n- \"Which integrations do you have?\", \"What can CRM Connector connect?\", \"Do you support Keap?\"\r\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.\r\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; `get_ai_agents_info` lists the systems it works with; follow the `explore-ai-agents` skill for questions about it). Then offer to show what travels between two of them.\r\n- Do not call `list_integrations` for this: that tool is only about the integrations a customer has set up.\r\n\r\n## What two systems can sync\r\n\r\n- \"Can I sync Pipedrive with Xero?\", \"What goes across between HubSpot and QuickBooks Online?\"\r\n- Call `find_sync_options` with both systems.\r\n- Say per record type:\r\n  - in which direction it travels, one way or both ways\r\n  - at which moment a record can travel, for example once an invoice is paid or a quote is accepted\r\n  - which filters apply, for example tags, pipeline stages or a minimum amount\r\n\r\n## Whether a field goes across\r\n\r\n- \"Does the phone number go across?\", \"Is the due date carried?\", \"Do the line items come along?\"\r\n- Call `get_field_details` with the two systems and the record type key.\r\n- Say plainly whether that field travels and how:\r\n  - **always**: it always goes across\r\n  - **needed**: the sync needs it, so it cannot be switched off\r\n  - **switchable**: the person can switch it off in the setup\r\n- Pass on notes such as \"only when the record is created\" and name what does not travel.\r\n\r\n## How to connect a system\r\n\r\n- \"How do I connect Xero?\", \"What do I need for GoHighLevel?\", \"Where do I find my token?\"\r\n- Call `get_connection_guide` with the system.\r\n- Give the steps in CRM Connector and, for each field it asks for, where to find it in that system.\r\n\r\n## Next step\r\n\r\n- Every answer from these tools carries a setup link: share it, so the person can start right away.\r\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.\r\n- When a system or combination is not offered, say so and share the request an integration link the tool gives.\r\n\r\n## Rules\r\n\r\n- Only describe what the tools return. Never promise a record type, direction, field or system the tools did not confirm.\r\n- Do not discuss prices, plans, trials or discounts.\r\n- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.\r\n"
AFTER
"---\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 2 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 `get_integration_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; `get_ai_agent_options` lists the systems it works with; follow the `plan-an-ai-agent` skill for questions about it). 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 `get_integration_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_integration_fields` 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 plan-an-integration 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 2 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 `get_integration_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; `get_ai_agent_options` lists the systems it works with; follow the `plan-an-ai-agent` skill for questions about it). 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 `get_integration_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_integration_fields` 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 plan-an-integration 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: 46766191ac46593c5861d4e5cd973ce7aff8fa4a51ddece190c63d6e388a6a84