Automation library · Alerts and monitoring

Send Emails from Slack with Gmail

Started by another system calling it, and works across Gmail and Slack. 12 steps, 3 branches: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
3Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 5Service 5

The steps in the order they run, from what starts it.

  1. 1Capture Slack EventsWebhookStarts it
  2. 2Adding a Auth Key for HTTPS requestSetLogic
  3. 3Check commandIfLogic
  4. 4Open Modal for Slash CommandHttp RequestService
  5. 5Parse Payload DataCodeLogic
  6. 6Check TypeIfLogic
  7. 7Check Email ValidationIfLogic
  8. 8Open Modal for ShortcutHttp RequestService
  9. 9Send an EmailGmailService
  10. 10Send Failure ResponseSlackService
  11. 11Send Success ResponseSlackService
  12. 12Respond to WebhookRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
12, with 3 branches
Size
Medium: a working afternoon
Connects to
Gmail, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 12 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.