Send client matter status updates from Clio via Twilio SMS and email
Ready for 3.0What this workflow does
This workflow has 32 nodes and runs when an HTTP POST request hits its webhook URL (plus 1 other trigger). Along the way it connects Twilio.
How it runs
Trigger: When an HTTP POST request hits its webhook URL (plus 1 other trigger).
- Parse Incoming Status SMS (Code): runs custom JavaScript code
- Parse Incoming Status Email (Code): runs custom JavaScript code
- Fetch Clio Contact By Phone (HTTP Request): calls an HTTP API (GET)
- Fetch Clio Contact By Email (HTTP Request): calls an HTTP API (GET)
- Match Client Using Phone Number (Code): runs custom JavaScript code
- Match Client Using Email Address (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- If: checks a condition and branches into true / false
- Check SMS Reply Cooldown (Code): runs custom JavaScript code
- Build Phone Client Not Found Reply (Code): runs custom JavaScript code
…plus 16 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (9)
- Webhook
n8n-nodes-base.webhook - Code
n8n-nodes-base.code - HTTP Request
n8n-nodes-base.httpRequest - If
n8n-nodes-base.if - Execute Sub-workflow
n8n-nodes-base.executeWorkflow - Twilio
n8n-nodes-base.twilio - No Operation, do nothing
n8n-nodes-base.noOp - Email Trigger (IMAP)
n8n-nodes-base.emailReadImap - Send Email
n8n-nodes-base.emailSend
From the author
Quick Overview This workflow responds to client case-status requests received via Twilio SMS or an IMAP inbox by matching the sender to a Clio contact, fetching the client’s open matters from Clio, and sending a status-only reply via SMS or email after a…