This workflow follows the HTTP Request → Slack recipe pattern — see all workflows that pair these two integrations.
The workflow JSON
Copy or download the full n8n JSON below. Paste it into a new n8n workflow, add your credentials, activate. Full import guide →
{
"name": "[DEPRECATED \u2014 use portal-internal-activity] T+3 \u2014 Follow-up (writes chatbot_activity)",
"nodes": [
{
"id": "t3-trigger",
"name": "T+3 Schedule Trigger",
"type": "n8n-nodes-base.scheduleTrigger",
"typeVersion": 1.2,
"position": [
250,
300
],
"parameters": {
"rule": {
"cronExpression": "0 9 * * *",
"timezone": "Europe/Madrid"
}
}
},
{
"id": "t3-resolve-clients",
"name": "Resolve Client",
"type": "n8n-nodes-base.code",
"typeVersion": 2,
"position": [
690,
300
],
"parameters": {
"jsCode": "// Scheduled flow \u2014 fetch clients due for T+3 follow-up.\n// A client is 'due' when onboarding_status='in_progress' AND\n// (now - go_live_at) is at least 3 days AND\n// no row exists in chatbot_activity for that client with event_type='t_plus_3_followup'.\nconst N_DAY = 3;\nconst resp = await this.helpers.httpRequest({\n method: 'GET',\n url: `${$env.SUPABASE_URL}/rest/v1/chatbot_clients?onboarding_status=eq.in_progress&go_live_at=lt.${new Date(Date.now() - N_DAY*86400e3).toISOString()}&select=id,company_name,primary_contact_email,slug`,\n headers: {\n apikey: $env.SUPABASE_SERVICE_ROLE_KEY,\n Authorization: `Bearer ${$env.SUPABASE_SERVICE_ROLE_KEY}`\n },\n json: true\n});\nif (!Array.isArray(resp) || resp.length === 0) { return []; }\nreturn resp.map((c) => ({ json: { client_id: c.id, company_name: c.company_name, contact_email: c.primary_contact_email, slug: c.slug } }));"
}
},
{
"id": "t3-build-id",
"name": "Build Activity Id (idempotent)",
"type": "n8n-nodes-base.code",
"typeVersion": 2,
"position": [
910,
300
],
"parameters": {
"jsCode": "// Deterministic UUIDv5 \u2014 see automations/t-plus-onboarding/README.md \u00a73.\nconst { v5: uuidv5 } = require('uuid');\nconst NAMESPACE = 'a1b2c3d4-e5f6-4a7b-8c9d-0e1f2a3b4c5d';\nconst ctx = $input.first().json;\nconst eventType = 't_plus_3_followup';\nconst dayOffset = 3;\nconst key = `${eventType}:${ctx.client_id}:${dayOffset}`;\nconst id = uuidv5(key, NAMESPACE);\nreturn [{ json: { ...ctx, activity_id: id, event_type: eventType, day_offset: dayOffset } }];"
}
},
{
"id": "t3-send-email",
"name": "Send T+3 Email",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
1130,
300
],
"parameters": {
"method": "POST",
"url": "https://api.resend.com/emails",
"authentication": "predefinedCredentialType",
"nodeCredentialType": "resendApi",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "Content-Type",
"value": "application/json"
}
]
},
"sendBody": true,
"bodyParameters": {
"parameters": [
{
"name": "from",
"value": "Kairikos <hola@kairikos.com>"
},
{
"name": "to",
"value": "={{ $json.contact_email }}"
},
{
"name": "subject",
"value": "Quick check-in \u2014 how is your chatbot doing?"
},
{
"name": "template",
"value": "t-plus-3-followup-v1"
},
{
"name": "data.company_name",
"value": "={{ $json.company_name }}"
}
]
},
"options": {
"timeout": 30000,
"retry": {
"maxTries": 3
}
}
}
},
{
"id": "t3-build-row",
"name": "Build Activity Row",
"type": "n8n-nodes-base.code",
"typeVersion": 2,
"position": [
1350,
300
],
"parameters": {
"jsCode": "// Assemble the final chatbot_activity row.\nconst emailResp = $input.first().json;\nconst ctx = $('Build Activity Id (idempotent)').first().json;\nconst row = {\n id: ctx.activity_id,\n client_id: ctx.client_id,\n day_offset: ctx.day_offset,\n event_type: ctx.event_type,\n title: \"T+3 follow-up sent\",\n body: null,\n metadata: {\n email_subject: \"Quick check-in \u2014 how is your chatbot doing?\",\n send_status: emailResp.id ? 'sent' : 'failed',\n provider: 'resend',\n email_message_id: emailResp.id || null,\n template: \"t-plus-3-followup-v1\",\n locale: 'es-ES'\n },\n occurred_at: new Date().toISOString()\n};\nreturn [{ json: row }];"
}
},
{
"id": "t3-upsert",
"name": "Upsert chatbot_activity",
"type": "n8n-nodes-base.httpRequest",
"typeVersion": 4.2,
"position": [
1570,
300
],
"parameters": {
"method": "POST",
"url": "={{ $env.SUPABASE_URL }}/rest/v1/chatbot_activity?on_conflict=id",
"sendHeaders": true,
"headerParameters": {
"parameters": [
{
"name": "apikey",
"value": "={{ $env.SUPABASE_SERVICE_ROLE_KEY }}"
},
{
"name": "Authorization",
"value": "Bearer {{ $env.SUPABASE_SERVICE_ROLE_KEY }}"
},
{
"name": "Content-Type",
"value": "application/json"
},
{
"name": "Prefer",
"value": "resolution=merge-duplicate,return=minimal"
}
]
},
"sendBody": true,
"body": "={{ JSON.stringify([$json]) }}",
"options": {
"timeout": 15000,
"retry": {
"maxTries": 3,
"waitBetween": 5000
}
}
}
},
{
"id": "t3-slack-err",
"name": "Notify Slack on Error",
"type": "n8n-nodes-base.slack",
"typeVersion": 2,
"position": [
1570,
520
],
"parameters": {
"channel": "#automation-alerts",
"text": ":rotating_light: T+3 flow failed for client `{{ $json.client_id }}` after 3 retries. Last error: {{ $json.error }}",
"otherOptions": {
"includeLinkToWorkflow": true
}
}
}
],
"connections": {
"T+3 Schedule Trigger": {
"main": [
[
{
"node": "Resolve Client",
"type": "main",
"index": 0
}
]
]
},
"Resolve Client": {
"main": [
[
{
"node": "Build Activity Id (idempotent)",
"type": "main",
"index": 0
}
]
]
},
"Build Activity Id (idempotent)": {
"main": [
[
{
"node": "Send T+3 Email",
"type": "main",
"index": 0
}
]
]
},
"Send T+3 Email": {
"main": [
[
{
"node": "Build Activity Row",
"type": "main",
"index": 0
}
]
],
"error": [
[
{
"node": "Notify Slack on Error",
"type": "main",
"index": 0
}
]
]
},
"Build Activity Row": {
"main": [
[
{
"node": "Upsert chatbot_activity",
"type": "main",
"index": 0
}
]
]
},
"Upsert chatbot_activity": {
"error": [
[
{
"node": "Notify Slack on Error",
"type": "main",
"index": 0
}
]
]
}
},
"settings": {
"executionOrder": "v1",
"saveExecutionProgress": true,
"saveManualExecutions": true,
"timezone": "Europe/Madrid"
},
"staticData": null,
"meta": {
"template": "kairikos-t-plus-onboarding",
"templateVersion": "1.0",
"dayOffset": 3,
"eventType": "t_plus_3_followup",
"author": "Automation Engineer",
"linkedIssue": "KAIA-734"
}
}
Pro
For the full experience including quality scoring and batch install features for each workflow upgrade to Pro
About this workflow
[DEPRECATED — use portal-internal-activity] T+3 — Follow-up (writes chatbot_activity). Uses httpRequest, slack. Scheduled trigger; 7 nodes.
Source: https://github.com/lagop/kairikos-chatbotAI-dash/blob/84b543e50315f28d1e83039e0d22e9097e8a51ab/automations/t-plus-onboarding/archive/t3-followup.json — original creator credit. Request a take-down →
Related workflows
Workflows that share integrations, category, or trigger type with this one. All free to copy and import.
Bet Assistant - Monitoring i Alerty Systemu. Uses httpRequest, slack, emailSend. Scheduled trigger; 10 nodes.
HTTP Request, Slack, Email Send
[DEPRECATED — use portal-internal-activity] T+7 — Follow-up (writes chatbot_activity). Uses httpRequest, slack. Scheduled trigger; 7 nodes.
HTTP Request, Slack
[DEPRECATED — use portal-internal-activity] T+14 — Follow-up (writes chatbot_activity). Uses httpRequest, slack. Scheduled trigger; 7 nodes.
HTTP Request, Slack
T+3 — Onboarding Email + Portal Activity (KAIA-756). Uses httpRequest, slack. Scheduled trigger; 6 nodes.
HTTP Request, Slack
T+7 — Onboarding Email + Portal Activity (KAIA-756). Uses httpRequest, slack. Scheduled trigger; 6 nodes.
HTTP Request, Slack