Salta ai contenuti

Workflow templates

Questi contenuti non sono ancora disponibili nella tua lingua.

Download a file and import it: n8n → Workflows → Import from file; Make → Create a new scenario → ⋯ → Import blueprint. Then pick your SynapsAI credential / connection and your agent in each SynapsAI step.

TemplateWhat it doesn8nMake
BSP pipelineYour messaging provider (BSP) posts each inbound message; SynapsAI answers; the reply goes back through the providerbsp-pipeline.jsoninbound + reply leg
CSAT radarEvery hour, conversations rated 1–2 go to Slackcsat-radar.jsoncsat-radar.json
Sheet → contacts → leadEach new spreadsheet row becomes a contact and the agent opens a qualifying conversationsheet-contacts-lead.jsonsheet-contacts-lead.json
Lead → CRMEvery captured lead is created or updated in HubSpotlead-to-crm.jsonlead-to-crm.json
Handoff → SlackWhen a customer asks for a person, your team is alerted with the conversation linkhandoff-to-slack.jsonhandoff-to-slack.json
Morning digestWeekdays at 08:00: yesterday’s conversations, average CSAT and leads by e-mailmorning-digest.jsonmorning-digest.json

Notes:

  • The BSP pipeline in n8n is one workflow (the SynapsAI node waits for the reply); in Make it is two scenarios — Ask agent sends the provider’s sender in metadata, and the reply leg reads it back from message.metadata.
  • Lead → CRM needs Capture leads on in the agent’s Memory & Learning (or a CRM extension): SynapsAI then captures one lead per closed conversation, and the same lead reaches every destination that is on.
  • Protect the BSP inbound webhook. Every request to it costs an agent turn. The n8n template uses Header Auth on its Webhook node — create the credential with a long random value and configure your provider to send it (or verify the provider’s own signature). In Make, set IP restrictions on the custom webhook to your provider’s addresses.
  • CSAT radar filters on the rating and then reads each conversation: a list item carries no score, the conversation does (csat.score, csat.feedback).
  • In Make, the triggers re-read each event with your key (see the Make quickstart); the BSP reply leg reads the sender from the conversation (externalUserId) and Lead → CRM reads the person with Get a contact.
  • Replace the example addresses (your-bsp.example, your-company.example, #cx-alerts, #support) with yours.