← LushaCONTENT HISTORY

Update to Lusha

Snapshot Nov 9, 2026 · 00:08 UTC · version 3.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Lusha and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Save Lusha contacts or companies from this conversation to a Lusha Workspace table, or export them to the user's CRM (Salesforce, HubSpot and other supported CRMs). Use when the user says \"save these to a table\", \"add them to my Lusha list\", \"put this in a Workspace table\", \"export to HubSpot\", \"push these to Salesforce\", \"send to my CRM\", \"sync these leads\", or picks the save or export next step at the end of another Lusha skill. Works on Lusha ids already in the conversation; to find new people or companies, use prospect, signal-prospect or lookalike-prospect first.\n",
  "included_files": [],
  "name": "save-or-export",
  "skill_md_contents": "---\nname: save-or-export\ndescription: \"Save Lusha contacts or companies from this conversation to a Lusha Workspace table, or export them to the user's CRM (Salesforce, HubSpot and other supported CRMs). Use when the user says \\\"save these to a table\\\", \\\"add them to my Lusha list\\\", \\\"put this in a Workspace table\\\", \\\"export to HubSpot\\\", \\\"push these to Salesforce\\\", \\\"send to my CRM\\\", \\\"sync these leads\\\", or picks the save or export next step at the end of another Lusha skill. Works on Lusha ids already in the conversation; to find new people or companies, use prospect, signal-prospect or lookalike-prospect first.\\n\"\n---\n\n# Save or Export\n\nThe last step of every Lusha workflow: put the result somewhere the user will work from it. Either a Lusha Workspace table (a saved list in the Lusha platform) or the user's CRM.\n\nOther skills hand off here with a set of records. When the user triggers this skill directly, collect the records from the conversation: the Lusha contact or company `id`s from earlier search, enrich, recommendation or scoring results. If there are none, say so and offer to find them first. Do not invent ids or search again for records the user already has.\n\n## Lusha call rules\n\n1. Pass `conversation_id` from the most recent Lusha response on every call. Start every `reason_for_invocation` with `save-or-export: `. When another skill handed off here, use that skill's name as the prefix instead, so the whole workflow is attributed to the skill the user started.\n2. If the last Lusha response carries `next_step_hints` and the user picked one of its offers, pass that hint's `ref` as `next_step_ref` on the call that carries it out.\n3. Before any call that uses quota already included in the user's existing Lusha account, state the existing-account quota it will use, and wait for the user to agree. This workflow cannot change the user's account entitlement.\n\n## Step 1 — Confirm what and where\n\nConfirm in one line: how many records, whether they are contacts or companies, and the destination (table, CRM, or both). A table holds one entity type, so contacts and companies go to separate tables.\n\n## Step 2a — Save to a Workspace table\n\n1. **Pick the table.** If the user named an existing table, find it with `table_list` (`name` filter, uses no quota) and use its `tableId`. Otherwise create one with `table_create`: `entity_type` `contacts` or `companies`, and a name that says what the list is and when it was made, e.g. `Fintech VPs Sales · 2026-10-26`. Leave `visibility` private unless the user asks to share it.\n2. **Add the records** with `table_add_entities`, up to 500 ids per call.\n   - **Contacts tables use no quota.** Pass `company_ids` index-aligned with `entity_ids` (each contact's Lusha company id) so the Workspace can enrich every row.\n   - **Companies tables use existing-account quota**: each newly added company uses the account's revealCompany quota rate (`account_usage` lists it). State the total first. The whole batch is reserved up front, so a batch the existing entitlement cannot cover fails with 402 and adds nothing. If the existing entitlement is insufficient, say so and offer to continue with a smaller batch. Never suggest changing the user's account entitlement.\n3. Report `added`, `alreadyPresent` and `invalidIds`, plus the table name and id.\n\nThe table holds the records only. Columns such as tier or score cannot be written into it, so a skill that ranked the list keeps the ranking in its own output (chat and CSV).\n\n## Step 2b — Export to the CRM\n\n1. **Check the connection first** with `get_supported_integrations` (uses no quota). It lists every supported CRM; read `isUserConnected` / `isAccountConnected`.\n   - **A 403:** the session is an API key, which this check can't read (it needs a Lusha login). Don't conclude there is no CRM. Ask which CRM they use, and export directly to it; the export tools accept a personal API key.\n   - **One CRM connected:** use its `integrationName` as `platform_name`.\n   - **Several connected:** ask which one.\n   - **None connected:** this is a setup step, not an error. Offer to connect: *\"Your Lusha account isn't connected to a CRM yet. Want a link to connect Salesforce, HubSpot or another CRM?\"* On yes, call `connect_crm` with the chosen `crm_type` and show the `redirectUrl` as a clickable link. The OAuth flow finishes in the browser, so check again with `get_supported_integrations` when the user says it's done. Connecting is admin-only: if the response says so, pass that on and suggest asking their Lusha admin. Do not retry.\n2. **Export** with `export_contacts_to_crm` (`contact_ids`) or `export_companies_to_crm` (`company_ids`), up to 100 ids per call; split larger lists. Contacts go in as the CRM's `Contact` object; on Salesforce, pass `object_name: \"Lead\"` when the user works leads.\n3. **Existing-account quota:** export uses quota per record the CRM actually writes; records already in the CRM or flagged duplicate use no quota. `account_usage` does not list the export quota rate, so say it uses quota per written record and report the quota used from the usage metadata afterwards.\n4. **Expired connection:** an error saying the connection expired (a 401) means the CRM must be re-authorized. No quota was used. Show its `redirectUrl` as a link. If the error doesn't carry the link, call `connect_crm` with the same CRM for a fresh one. Retry the export once the user says they've reconnected. A CRM marked `isAccountConnected` but not `isUserConnected` often lands here.\n5. If the CRM tools are not available in this session, the account's plan does not include CRM export. Say so and offer the Workspace table instead.\n\n## Step 3 — Report\n\n| Destination | Added / exported | Already there | Failed | Existing-account quota used |\n|---|---|---|---|---|\n\n- For a table, give its name.\n- For CRM, list the `crmLink` of up to 10 exported records and the `error` of any failure.\n\nThen return to the skill that handed off, if any, for its closing suggestion. If the user came here directly, suggest `score-my-list` to rank what they just saved.\n"
}

SHA-256 of public snapshot: 4c85678bf38c3325db4c64ba1a8a731e77dac2c5d3ee5a026af2fd31da6ddb22