DEV Community

Cover image for Automating a manual workflow with n8n: a step-by-step example
Saawahi IT Solution
Saawahi IT Solution

Posted on

Automating a manual workflow with n8n: a step-by-step example

Every week, someone on our team did the same thing: open a form response, copy the details into a spreadsheet, post a note in Slack, and send the person a confirmation email. It took about ten minutes per submission and was easy to get wrong. This post walks through automating it with n8n, step by step, so you can adapt the same pattern to your own process.

What we're automating

When someone submits a form:

  1. Save the response as a new row in a Google Sheet.
  2. Send a message to a Slack channel with the key details.
  3. Send the submitter a confirmation email.
  4. If the request is marked "urgent", also ping a specific person.

Step 1: Create the trigger

Add a Google Sheets Trigger node set to "Row Added", or a Webhook node if your form tool can send a POST request. The Webhook is more flexible: it works with almost any form builder, and you can test it by sending a sample payload.

Activate the workflow and submit a test entry. The node's output panel shows the data n8n received. Check this before you build anything else.

Step 2: Clean up the data

Add a Set node (called "Edit Fields" in recent versions) to pick out the fields you need and give them clear names:

name     = {{ $json.body.name }}
email    = {{ $json.body.email }}
request  = {{ $json.body.request }}
priority = {{ $json.body.priority }}
Enter fullscreen mode Exit fullscreen mode

Use the field paths from your own test output, since they depend on your form tool. Normalizing names here keeps the later steps readable.

Step 3: Save to a sheet

Add a Google Sheets node with the operation “Append”. Map each column to one of the fields from Step 2, and add a timestamp using {{ $now.toISO() }}.

Appending rather than updating means you keep a full history, which is what most teams want from a log.

Step 4: Route urgent requests

Add an IF node with the condition priorityequals urgent. It has two outputs:

  • True: send a direct Slack message to the on-call person.

  • False: send only the regular channel notification.

Keeping the branches separate makes it easy to change the rule later without touching the rest of the flow.

Step 5: Notify Slack and email the submitter

Add a Slack node that posts to your channel, for example:

New request from {{ $json.name }} ({{ $json.priority }}):
{{ $json.request }}
Enter fullscreen mode Exit fullscreen mode

Then add a Gmail (or SMTP) node to send the confirmation email to {{ $json.email }}. Keep the email short: say what you received and when someone will reply.

Step 6: Handle failures

Automations fail quietly if nobody watches them. Three simple safeguards:

  • Turn on Retry on Fail for the Sheets, Slack and email nodes.

  • Use an Error Trigger workflow to send yourself an alert when any run fails.

  • Log the form payload to a separate sheet so you can replay a missed submission.

Results

After testing with 30 submissions, every entry reached the sheet, the channel and the submitter. Setup took an afternoon. Since then, the team has spent that ten minutes per submission on the actual requests instead.

Next steps

  • Export the workflow as JSON and store it in version control.

  • Add a daily summary run with a Schedule Trigger.

  • If your process has an approval step, add a Wait node before the email
    If you want help building workflows automation like this for your own operations, Saawahi IT Solution works on automation and custom software.

Top comments (0)