CRM API Step

Call your connected CRM's API with Spara's stored connection and extract data from the response.

The CRM API step makes an authenticated request to your connected CRM — Salesforce, HubSpot, or Marketo — and optionally extracts data from the response into lead fields for use in downstream steps.

It works like the API Step step, but you don't manage credentials or build the full URL. Spara uses the CRM connection you already set up under Settings → Integrations, refreshes the access token when it expires, and prepends the CRM's base URL to the endpoint you enter.

Only organization admins can add a CRM API step to a workflow.

Configuration

CRM

Choose the CRM to call. Only CRMs your organization has connected are selectable; a CRM that needs to be reconnected is flagged, and the step won't run until it is reconnected in Settings → Integrations.

Method and endpoint

Select the HTTP method (GET, POST, PUT, or PATCH) and enter the endpoint path. Spara prepends the CRM's base URL:

CRM	Base URL
Salesforce	Your Salesforce instance URL (e.g., https://acme.my.salesforce.com)
HubSpot	https://api.hubapi.com
Marketo	Your Marketo REST host (e.g., https://123-ABC-456.mktorest.com)

The endpoint supports variables, so you can address a specific record using lead data. Insert them from the Insert menu (⚡) or by typing {{. For example:

/crm/v3/objects/contacts/{{ hubspot_contact_id }}

Variable values are URL-encoded automatically, so characters like @, +, and spaces are sent safely and a value can't change the rest of the endpoint. A field with no value for the lead is left blank.

The endpoint must be a path relative to the CRM's base URL — a full URL or a path that navigates above the base is rejected.

Headers

Add request headers as key/value pairs. Spara sets the Authorization header from your CRM connection, so you never enter a token here.

Body

For POST, PUT, and PATCH requests, enter the request body as JSON. The editor provides syntax highlighting, inline validation, a Format button, and the Insert menu (⚡) for variables — the same as the API step.

{
  "properties": {
    "lifecyclestage": "salesqualifiedlead",
    "spara_intent_score": "{{ intent_score }}"
  }
}

Field Extraction

After the request completes, Spara can extract values from the response and save them as lead fields, available as variables in downstream steps.

Field	Description
Name	The field name (e.g., owner_email). Use snake_case.
Description	Tell the AI what this field represents and where to find it in the response.

Example: Look up a HubSpot contact's owner

CRM: HubSpot
GET /crm/v3/objects/contacts/{{ hubspot_contact_id }}?properties=hubspot_owner_id,lifecyclestage

Field Extraction:
- Name: hubspot_owner_id
  Description: The contact's owner ID from "properties.hubspot_owner_id"
- Name: lifecycle_stage
  Description: The contact's lifecycle stage from "properties.lifecyclestage"

Downstream steps can then branch on {{ lifecycle_stage }} or include {{ hubspot_owner_id }} in a notification.