---
title: "Automation"
description: "Automate workflows with Sarah using Make or Zapier — safe overview"
keywords: ["automation", "make", "zapier", "workflows"]
lastUpdated: "2026-04-07"
---

# Automation

Sarah can work with tools like **Make** and **Zapier** so repetitive tasks run without manual work—when your plan supports it. This guide stays **high level** on purpose: it does **not** list internal URLs, JSON examples, or authentication headers.

## Why automate

- Less manual data entry between Sarah and other apps  
- Faster notifications to your team or customers  
- Fewer mistakes when the same steps happen on every sale or stock change  

## Platforms

| Tool | Best for |
|------|----------|
| **Make** | Visual scenarios, several steps, richer logic |
| **Zapier** | Quick connections and large app directory |

Use each vendor’s **official help center** to learn how to build scenarios, webhooks, and HTTP actions.

## How to start safely

1. In Sarah, open **Settings > Integrations** and handle keys only from that screen.  
2. In Make/Zapier, create a workflow using their UI—never embed production keys in public demo projects.  
3. Test with **sandbox / test data** from the other platform before touching live customers.  
4. If a credential might have leaked, **rotate it** in Sarah immediately.

## Example ideas (availability varies)

- Mirror **inventory or catalog** data between Sarah and an external system.  
- Post to **Slack, Discord, or email** when important events happen in Sarah.  
- Kick off tasks in another app when a sale or invoice is created—**if** your account allows it.

Confirm what you are allowed to do with **Sarah support** if you are unsure.

## Where to read more (public)

- [Webhooks overview](/docs/api/webhooks) — policy-focused summary  
- [Make and Zapier](/docs/api/integrations/make-zapier) — merchant checklist  
- [Integrations](/docs/api/integrations) — payments, shipping, WhatsApp, etc.

## Support

Send your **account name** and a plain-language description of the workflow. **Do not** paste secret keys in tickets.