Prospect CRM Push

skill

Create new prospect contacts in the CRM via POST and stage updates to existing records for a human.

Download .md

Prospect CRM Push

Create new prospect contacts in the CRM (customer relationship management system) and stage proposed edits to existing records for a human to apply.

When to use

  • A new prospect has been identified and needs to be added to the CRM as a contact.
  • Research or outreach has surfaced updated details (title, company, phone, notes) for a contact that already exists in the CRM.
  • A batch of prospects needs to be pushed into the CRM after a sourcing run.
  • A stale or incomplete CRM record needs a correction that only a human can apply.

Tools

  • http-post — calls the CRM's REST API to create new prospect contact records.
  • write-file — writes the staged update list (proposed changes to existing records) to a file for human review.
  • send-message — notifies a human that new contacts were created and/or that staged updates are waiting for their action.

Playbook

  1. Confirm you have the prospect's core fields ready: name, email, company, title, and any source/context notes.
  2. Check whether the prospect already exists in the CRM before creating a duplicate, using the CRM's search/read capability if available in this session.
  3. For a brand-new prospect, call the CRM REST API with http-post (e.g. POST https://api.hubapi.com/crm/v3/objects/contacts) to create the contact record. Authentication is injected by the org's Integration row for this host — never ask for, echo, or hardcode credentials.
  4. If the create call returns 401/403 or no Integration row exists for the CRM host, stop and message a human via send-message asking them to create the Integration, naming the service and required scopes.
  5. If the create call succeeds, note the new record's ID and confirm the fields that were written.
  6. For an existing prospect that needs updating, do not attempt the change directly — the CRM's update path requires PATCH/PUT, which is not possible with the declared tools. Instead, compile the proposed field changes (record ID, field name, old value, new value) into a clear change list.
  7. Write the change list to a file with write-file so a human can review and apply it in the CRM.
  8. Message a human via send-message, pointing them to the staged file and summarizing how many new contacts were created and how many updates are pending their action.
  9. If a batch of prospects is being processed, repeat the create/stage steps for each one and roll the summary into a single final send-message.

Failure modes

  • 401/403 on the CRM API call -> missing Integration row; stop and escalate via send-message naming the service and required scopes.
  • Create call returns an empty or unexpected result -> verify the endpoint URL and required parameters before retrying.
  • Rate limit or throttling response from the CRM -> back off, retry later, and note the rate limit in memory for future runs.
  • CRM record needs a field update or deletion -> not possible with declared tools; write the change to a file with write-file and hand off to a human via send-message rather than implying the update happened.

Done when

  • Each new prospect has a confirmed contact record ID returned from the http-post create call.
  • A change-list file exists (via write-file) enumerating every proposed update to existing records.
  • A human has been notified via send-message with a summary of contacts created and updates staged for their review.