> For the complete documentation index, see [llms.txt](https://docs.spara.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spara.com/build/workflows/steps.md).

# Workflow Steps

The individual actions a workflow can run, from sending an email to branching on a condition.

**Steps** are the individual actions in a [Workflows](https://docs.spara.com/build/workflows.md). Each step executes in sequence: when one finishes, the next begins. Use **Wait** steps to control timing, and **Condition** steps to branch the logic.

<figure><img src="https://4072969777-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FreCGkFdsmuPJzGP9ZgGA%2Fuploads%2Fgit-blob-3faa4ae77cd27bce2ea1cae85e22a8e4af5ea36a%2FWorkflow%20Editor.png?alt=media" alt=""><figcaption><p>A workflow assembled from steps, with branching logic.</p></figcaption></figure>

| Step                                                                          | What it does                                                                                                                 |
| ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [Send Email Step](https://docs.spara.com/build/workflows/steps/send-email.md) | Sends a personalized email to the lead or their assigned rep.                                                                |
| [Send Text Step](https://docs.spara.com/build/workflows/steps/send-text.md)   | Sends an SMS to the lead's phone number.                                                                                     |
| [Call Phone Step](https://docs.spara.com/build/workflows/steps/call-phone.md) | Uses the Phone capability to call the lead's phone number.                                                                   |
| [Notify Step](https://docs.spara.com/build/workflows/steps/notify.md)         | Sends a Slack or Microsoft Teams notification to your team.                                                                  |
| [Wait Step](https://docs.spara.com/build/workflows/steps/wait.md)             | Pauses execution for a set duration (up to 30 days).                                                                         |
| [Condition Step](https://docs.spara.com/build/workflows/steps/condition.md)   | Branches workflow logic based on lead data.                                                                                  |
| [API Step](https://docs.spara.com/build/workflows/steps/api.md)               | Makes an HTTP request to an external system and can extract data.                                                            |
| [CRM API Step](https://docs.spara.com/build/workflows/steps/crm-api.md)       | Calls your connected CRM (Salesforce, HubSpot, or Marketo) using Spara's stored connection and can extract data. Admin only. |
| [Set Field Step](https://docs.spara.com/build/workflows/steps/set-field.md)   | Writes a value you specify to a field on the lead.                                                                           |
| [Research Step](https://docs.spara.com/build/workflows/steps/research.md)     | Researches a lead or company with an AI prompt (with web search) and extracts structured data.                               |

{% hint style="warning" %}
If a step cannot execute (e.g., a **Call Phone** step for a lead with no phone number), the workflow skips it and continues to the next step.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.spara.com/build/workflows/steps.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
