Update to CRM Connector
Snapshot Oct 31, 2026 · 15:03 UTC · version 1.1.2
Collection source: downloaded plugin package.
Instructions updated for set-up-a-sync
Skill instructions — Now says: --- name: set-up-a-sync description: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants...
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
--- name: set-up-a-sync description: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example "when a deal is won in HubSpot, ma...
Oct 31, 2026 · 15:03 UTC
--- name: set-up-a-sync description: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example "when a deal is won in HubSpot, make...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,45 +1,45 @@ ---- -name: set-up-a-sync -description: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example "when a deal is won in HubSpot, make a draft invoice in QuickBooks Online" or "keep my Xero contacts in Pipedrive". ---- - -# Set up a sync with CRM Connector - -This belongs to part 1 of the plugin, **Integrations between two systems**: an integration set up once that then keeps two systems in sync by itself. Work inside one system (reading, changing or automating its records) is part 2, AI Agents: `get_ai_access` explains it. - -CRM Connector keeps business systems in sync: contacts, invoices, quotes, deals, jobs and appointments travel between systems such as QuickBooks Online, Xero, Jobber, HubSpot, Pipedrive and Salesforce. This skill turns a wish into a plan; the CRM Connector tools hold the facts. - -## Steps - -1. **Know the two systems and what should travel.** If either is unclear, ask one short question, for example "Which system do the deals start in, and where should the invoices end up?" Never guess a system. -2. **Check what is possible.** Call `find_sync_options` with both systems. Use what it returns: the record types, the direction (one way, or both ways for the record types it marks), the moments a record can wait for (such as when paid or when accepted) and the filters. -3. **Make the plan.** Call `plan_integration` with: - - the source system and the target system - - the record type keys `find_sync_options` returned - - the trigger, when the person asked for one - - `direction` `both_ways` when changes made in either system should reach the other; leave it out for one way - - When the person is signed in and allowed "Manage your integrations", `create_integration` takes the same arguments and creates the integration right away, after they confirm what will be created. -4. **Share the link and what happens next.** - - Share the setup link from the plan as a link. - - They open it, sign in or create a CRM Connector account, connect both systems and review every choice before anything syncs. - - Pass on the plan's notes, for example that contacts travel along, that a sync from date is needed, or which record types stay one way when both ways was asked. - -## Spreadsheets (Google Sheets, an Excel or CSV file) - -- A spreadsheet only sends: records go from the sheet into the other system and nothing is written back. -- Call `find_sync_options` with the spreadsheet and the other system, or `how_to_connect` with `other_system`. Its `sheet` part holds our template made for that system. Recommend it first, because its columns match by themselves: share the template download link, name the tabs and the required columns, and pass on the steps for using it. -- With a sheet of their own, they match its columns to the fields of the other system in the setup; pass on the tool's sentence about it. -- For a spreadsheet, `get_field_details` names each field by the column of our template. - -## When something is not offered - -- Say so plainly and share the request an integration link the tool gives. -- When a tool says the other direction is possible, offer that instead. - -## Rules - -- Only describe what the tools return. Never promise a record type, a direction, a trigger or a system the tools did not confirm. -- `create_integration` creates an integration, so ask the person to confirm first: say what it will create (the two systems, the record types and the direction) before calling it. It needs "Manage your integrations" on the consent page; without it, use `plan_integration` and share the setup link. No tool deletes an integration or a connection. -- Do not discuss prices, plans, trials or discounts. If a tool says the account has no active plan, pass on its sentence and link exactly as given. -- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation. +--- +name: set-up-a-sync +description: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example "when a deal is won in HubSpot, make a draft invoice in QuickBooks Online" or "keep my Xero contacts in Pipedrive". +--- + +# Set up a sync with CRM Connector + +This belongs to part 1 of the plugin, **Integrations between two systems**: an integration set up once that then keeps two systems in sync by itself. Work inside one system (reading, changing or automating its records) is part 2, AI Agents: `get_ai_agents_info` explains it. + +CRM Connector keeps business systems in sync: contacts, invoices, quotes, deals, jobs and appointments travel between systems such as QuickBooks Online, Xero, Jobber, HubSpot, Pipedrive and Salesforce. This skill turns a wish into a plan; the CRM Connector tools hold the facts. + +## Steps + +1. **Know the two systems and what should travel.** If either is unclear, ask one short question, for example "Which system do the deals start in, and where should the invoices end up?" Never guess a system. +2. **Check what is possible.** Call `find_sync_options` with both systems. Use what it returns: the record types, the direction (one way, or both ways for the record types it marks), the moments a record can wait for (such as when paid or when accepted) and the filters. +3. **Make the plan.** Call `plan_integration` with: + - the source system and the target system + - the record type keys `find_sync_options` returned + - the trigger, when the person asked for one + - `direction` `both_ways` when changes made in either system should reach the other; leave it out for one way + When they change their mind, call `plan_integration` again: that saves a new concept with its own link and leaves the earlier one as it is, so share the newest link. +4. **Share the link and what happens next.** + - Share the setup link from the plan as a link. + - Say the plan is saved as a concept: nothing syncs yet, and they find it again under Integrations in CRM Connector. + - They open it, sign in or create a CRM Connector account, connect both systems and review every choice before anything syncs. + - Pass on the plan's notes, for example that contacts travel along, that a sync from date is needed, or which record types stay one way when both ways was asked. + +## Spreadsheets (Google Sheets, an Excel or CSV file) + +- A spreadsheet only sends: records go from the sheet into the other system and nothing is written back. +- Call `find_sync_options` with the spreadsheet and the other system, or `get_connection_guide` with `other_system`. Its `sheet` part holds our template made for that system. Recommend it first, because its columns match by themselves: share the template download link, name the tabs and the required columns, and pass on the steps for using it. +- With a sheet of their own, they match its columns to the fields of the other system in the setup; pass on the tool's sentence about it. +- For a spreadsheet, `get_field_details` names each field by the column of our template. + +## When something is not offered + +- Say so plainly and share the request an integration link the tool gives. +- When a tool says the other direction is possible, offer that instead. + +## Rules + +- Only describe what the tools return. Never promise a record type, a direction, a trigger or a system the tools did not confirm. +- No tool creates the integration itself: the person creates it in CRM Connector from the setup link, after reviewing every choice. No tool deletes an integration or a connection. +- Do not discuss prices, plans, trials or discounts. If a tool says the account has no active plan, pass on its sentence and link exactly as given. +- 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
"---\r\nname: set-up-a-sync\r\ndescription: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example \"when a deal is won in HubSpot, make a draft invoice in QuickBooks Online\" or \"keep my Xero contacts in Pipedrive\".\r\n---\r\n\r\n# Set up a sync with CRM Connector\r\n\r\nThis belongs to part 1 of the plugin, **Integrations between two systems**: an integration set up once that then keeps two systems in sync by itself. Work inside one system (reading, changing or automating its records) is part 2, AI Agents: `get_ai_access` explains it.\r\n\r\nCRM Connector keeps business systems in sync: contacts, invoices, quotes, deals, jobs and appointments travel between systems such as QuickBooks Online, Xero, Jobber, HubSpot, Pipedrive and Salesforce. This skill turns a wish into a plan; the CRM Connector tools hold the facts.\r\n\r\n## Steps\r\n\r\n1. **Know the two systems and what should travel.** If either is unclear, ask one short question, for example \"Which system do the deals start in, and where should the invoices end up?\" Never guess a system.\r\n2. **Check what is possible.** Call `find_sync_options` with both systems. Use what it returns: the record types, the direction (one way, or both ways for the record types it marks), the moments a record can wait for (such as when paid or when accepted) and the filters.\r\n3. **Make the plan.** Call `plan_integration` with:\r\n - the source system and the target system\r\n - the record type keys `find_sync_options` returned\r\n - the trigger, when the person asked for one\r\n - `direction` `both_ways` when changes made in either system should reach the other; leave it out for one way\r\n\r\n When the person is signed in and allowed \"Manage your integrations\", `create_integration` takes the same arguments and creates the integration right away, after they confirm what will be created.\r\n4. **Share the link and what happens next.**\r\n - Share the setup link from the plan as a link.\r\n - They open it, sign in or create a CRM Connector account, connect both systems and review every choice before anything syncs.\r\n - Pass on the plan's notes, for example that contacts travel along, that a sync from date is needed, or which record types stay one way when both ways was asked.\r\n\r\n## Spreadsheets (Google Sheets, an Excel or CSV file)\r\n\r\n- A spreadsheet only sends: records go from the sheet into the other system and nothing is written back.\r\n- Call `find_sync_options` with the spreadsheet and the other system, or `how_to_connect` with `other_system`. Its `sheet` part holds our template made for that system. Recommend it first, because its columns match by themselves: share the template download link, name the tabs and the required columns, and pass on the steps for using it.\r\n- With a sheet of their own, they match its columns to the fields of the other system in the setup; pass on the tool's sentence about it.\r\n- For a spreadsheet, `get_field_details` names each field by the column of our template.\r\n\r\n## When something is not offered\r\n\r\n- Say so plainly and share the request an integration link the tool gives.\r\n- When a tool says the other direction is possible, offer that instead.\r\n\r\n## Rules\r\n\r\n- Only describe what the tools return. Never promise a record type, a direction, a trigger or a system the tools did not confirm.\r\n- `create_integration` creates an integration, so ask the person to confirm first: say what it will create (the two systems, the record types and the direction) before calling it. It needs \"Manage your integrations\" on the consent page; without it, use `plan_integration` and share the setup link. No tool deletes an integration or a connection.\r\n- Do not discuss prices, plans, trials or discounts. If a tool says the account has no active plan, pass on its sentence and link exactly as given.\r\n- Never ask for passwords, API keys or tokens. Systems are connected inside the CRM Connector app, never in the conversation.\r\n"
"---\nname: set-up-a-sync\ndescription: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example \"when a deal is won in HubSpot, make a draft invoice in QuickBooks Online\" or \"keep my Xero contacts in Pipedrive\".\n---\n\n# Set up a sync with CRM Connector\n\nThis belongs to part 1 of the plugin, **Integrations between two systems**: an integration set up once that then keeps two systems in sync by itself. Work inside one system (reading, changing or automating its records) is part 2, AI Agents: `get_ai_agents_info` explains it.\n\nCRM Connector keeps business systems in sync: contacts, invoices, quotes, deals, jobs and appointments travel between systems such as QuickBooks Online, Xero, Jobber, HubSpot, Pipedrive and Salesforce. This skill turns a wish into a plan; the CRM Connector tools hold the facts.\n\n## Steps\n\n1. **Know the two systems and what should travel.** If either is unclear, ask one short question, for example \"Which system do the deals start in, and where should the invoices end up?\" Never guess a system.\n2. **Check what is possible.** Call `find_sync_options` with both systems. Use what it returns: the record types, the direction (one way, or both ways for the record types it marks), the moments a record can wait for (such as when paid or when accepted) and the filters.\n3. **Make the plan.** Call `plan_integration` with:\n - the source system and the target system\n - the record type keys `find_sync_options` returned\n - the trigger, when the person asked for one\n - `direction` `both_ways` when changes made in either system should reach the other; leave it out for one way\n When they change their mind, call `plan_integration` again: that saves a new concept with its own link and leaves the earlier one as it is, so share the newest link.\n4. **Share the link and what happens next.**\n - Share the setup link from the plan as a link.\n - Say the plan is saved as a concept: nothing syncs yet, and they find it again under Integrations in CRM Connector.\n - They open it, sign in or create a CRM Connector account, connect both systems and review every choice before anything syncs.\n - Pass on the plan's notes, for example that contacts travel along, that a sync from date is needed, or which record types stay one way when both ways was asked.\n\n## Spreadsheets (Google Sheets, an Excel or CSV file)\n\n- A spreadsheet only sends: records go from the sheet into the other system and nothing is written back.\n- Call `find_sync_options` with the spreadsheet and the other system, or `get_connection_guide` with `other_system`. Its `sheet` part holds our template made for that system. Recommend it first, because its columns match by themselves: share the template download link, name the tabs and the required columns, and pass on the steps for using it.\n- With a sheet of their own, they match its columns to the fields of the other system in the setup; pass on the tool's sentence about it.\n- For a spreadsheet, `get_field_details` names each field by the column of our template.\n\n## When something is not offered\n\n- Say so plainly and share the request an integration link the tool gives.\n- When a tool says the other direction is possible, offer that instead.\n\n## Rules\n\n- Only describe what the tools return. Never promise a record type, a direction, a trigger or a system the tools did not confirm.\n- No tool creates the integration itself: the person creates it in CRM Connector from the setup link, after reviewing every choice. No tool deletes an integration or a connection.\n- Do not discuss prices, plans, trials or discounts. If a tool says the account has no active plan, pass on its sentence and link exactly as given.\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": "Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example \"when a deal is won in HubSpot, make a draft invoice in QuickBooks Online\" or \"keep my Xero contacts in Pipedrive\".",
"included_files": [],
"name": "set-up-a-sync",
"skill_md_contents": "---\nname: set-up-a-sync\ndescription: Turn an integration someone describes into a CRM Connector plan with a prefilled setup link. Use it when a person wants two business systems connected, for example \"when a deal is won in HubSpot, make a draft invoice in QuickBooks Online\" or \"keep my Xero contacts in Pipedrive\".\n---\n\n# Set up a sync with CRM Connector\n\nThis belongs to part 1 of the plugin, **Integrations between two systems**: an integration set up once that then keeps two systems in sync by itself. Work inside one system (reading, changing or automating its records) is part 2, AI Agents: `get_ai_agents_info` explains it.\n\nCRM Connector keeps business systems in sync: contacts, invoices, quotes, deals, jobs and appointments travel between systems such as QuickBooks Online, Xero, Jobber, HubSpot, Pipedrive and Salesforce. This skill turns a wish into a plan; the CRM Connector tools hold the facts.\n\n## Steps\n\n1. **Know the two systems and what should travel.** If either is unclear, ask one short question, for example \"Which system do the deals start in, and where should the invoices end up?\" Never guess a system.\n2. **Check what is possible.** Call `find_sync_options` with both systems. Use what it returns: the record types, the direction (one way, or both ways for the record types it marks), the moments a record can wait for (such as when paid or when accepted) and the filters.\n3. **Make the plan.** Call `plan_integration` with:\n - the source system and the target system\n - the record type keys `find_sync_options` returned\n - the trigger, when the person asked for one\n - `direction` `both_ways` when changes made in either system should reach the other; leave it out for one way\n When they change their mind, call `plan_integration` again: that saves a new concept with its own link and leaves the earlier one as it is, so share the newest link.\n4. **Share the link and what happens next.**\n - Share the setup link from the plan as a link.\n - Say the plan is saved as a concept: nothing syncs yet, and they find it again under Integrations in CRM Connector.\n - They open it, sign in or create a CRM Connector account, connect both systems and review every choice before anything syncs.\n - Pass on the plan's notes, for example that contacts travel along, that a sync from date is needed, or which record types stay one way when both ways was asked.\n\n## Spreadsheets (Google Sheets, an Excel or CSV file)\n\n- A spreadsheet only sends: records go from the sheet into the other system and nothing is written back.\n- Call `find_sync_options` with the spreadsheet and the other system, or `get_connection_guide` with `other_system`. Its `sheet` part holds our template made for that system. Recommend it first, because its columns match by themselves: share the template download link, name the tabs and the required columns, and pass on the steps for using it.\n- With a sheet of their own, they match its columns to the fields of the other system in the setup; pass on the tool's sentence about it.\n- For a spreadsheet, `get_field_details` names each field by the column of our template.\n\n## When something is not offered\n\n- Say so plainly and share the request an integration link the tool gives.\n- When a tool says the other direction is possible, offer that instead.\n\n## Rules\n\n- Only describe what the tools return. Never promise a record type, a direction, a trigger or a system the tools did not confirm.\n- No tool creates the integration itself: the person creates it in CRM Connector from the setup link, after reviewing every choice. No tool deletes an integration or a connection.\n- Do not discuss prices, plans, trials or discounts. If a tool says the account has no active plan, pass on its sentence and link exactly as given.\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: 11417c2f9707fd0075d041803d02f0a9f70863aaa68c51e4bc321e6e23ed2405