Guides

End-to-end recipes that combine Salfio integrations, webhooks, and Claude Code routines to automate real workflows.

The reference docs explain what each Salfio surface does. These guides show what to build with them. Most recipes stitch multiple pieces together — a Salfio integration, an outbound webhook, a Claude Code routine — and walk you from prerequisites to a verified, working automation; others are straight API how-tos you can drop into your own onboarding scripts.

The Salfio assistant — in the Slack @mention/DM and the dashboard chat — can create and update clients, set labels, add notes, answer integration questions, and manage channel assignment rules conversationally. Destructive actions always ask for confirmation first.

When a meeting captured by Salfio's meeting bot lands in your activity stream, fire a Claude Code routine that drafts a recap email straight into your Gmail Drafts folder. The routine pulls client context and conversation history from Salfio so the recap reads like you wrote it.

When a new email lands in Salfio via Gmail, fire a Claude Code routine that writes the reply you'd send and saves it as a Gmail draft. The routine reads the open thread, prior commitments, and the tone you use with that client before drafting.

Discover your organization's integrations and a Slack integration's channels, then bind a channel to a client so its messages are assigned automatically — entirely over the API or MCP, no dashboard. The recipe for onboarding clients programmatically.

Render Salfio cards in your own product, and send back the ones your users reject. Read a client's cards to get the card value id, then post a category and your user's own words against it — so card quality is measured against real signal instead of anecdotes.

The automation recipes wire the same three pieces: integrations supply the data, a Salfio webhook fires the event, and a Claude Code routine acts on it. Once you've completed one of those, the next is mostly a swap of the event type and the routine prompt — the connectors, the credential flow, and the webhook configuration are the same.

The API recipes — assigning a Slack channel, forwarding card feedback — need none of that machinery. They are plain HTTP against api.salfio.com/v1 with a Bearer key, and drop straight into an onboarding script or your own product's UI.

If you're new to Salfio webhooks, skim the Webhooks reference first — it covers the payload envelope, transports, and retry behaviour these recipes build on.