DEV Community: Stackscale

Automate Slack Standups & Team Welcomes (No Code Workflow)

Stackscale — Sat, 07 Nov 2026 05:29:27 +0000

If you want to automate Slack standups, two no-code workflows can collect every answer and welcome every new member for you. No more chasing updates in DMs, and no new joiner left guessing where to start.

What you need

A Slack workspace with Workflow Builder access
Optional: a Make account, if you want a permanent log of standup answers

Disclosure: Some links below are affiliate links, meaning StackScale may earn a commission at no extra cost to you.

Get started with Make here: https://www.make.com/en/register?pc=stackscale&affiliateSource=devto

The two workflows

Standup collector — scheduled, asks three questions every weekday, posts every answer to #standup.
Welcome greeter — triggered when someone joins, sends a welcome DM with a checklist.

Step 1: Schedule the standup trigger

Open Workflow Builder and create a workflow that starts on a schedule. Set it to run at 9 AM, Monday to Friday. Nobody has to remember to start the standup — it just happens.

Step 2: Ask three questions

Add a form step with three short questions:

What did you do yesterday?
What are you doing today?
What is blocking you?

Keep each answer to one or two sentences.

Step 3: Post every answer to #standup

Add a step that sends each answer to your standup channel in the same format, with the person's name attached. Open one channel, scan three answers per person, and you know exactly where the team stands.

Example answer payload (dummy data):

{
  "user": "Alex Carter",
  "yesterday": "Shipped the onboarding flow",
  "today": "Fixing the checkout bug",
  "blockers": "Waiting on API keys"
}

Step 4: Build the welcome workflow

This one starts when a person joins a channel — the trigger is a new member joining, so it runs itself the moment someone arrives. Add a step that sends the new member a direct message: welcome them by name, link the team handbook, list the three channels to join first, and give them a short checklist — introduce yourself, set your working hours, and post your first standup answer.

Step 5 (optional): Log answers with Make

If you want a permanent record, add one Make scenario: watch the #standup channel for new messages, then add each answer as a row in a Google Sheet or a Notion database. Map the fields like this:

Standup field	Sheet / Notion column
User	Name
Yesterday	Yesterday
Today	Today
Blockers	Blockers

You get a searchable history of blockers and progress without anyone typing anything twice.

Step 6: Test with dummy data

Before turning it on for the whole team, submit a standup answer as a test user and check it appears in the channel in the right format. Join the welcome channel with a test account and check the greeting arrives.

The habit that makes it work

Every morning, open the #standup channel first, read the blockers before anything else, and unblock one person before your first meeting. A standup only works if blockers actually get cleared.

Watch the full tutorial above. New automation tutorial every day on the StackScale YouTube channel.

Build a Simple CRM in Notion (No Code) — Track Leads Like a Pro

Stackscale — Sat, 07 Nov 2026 05:28:26 +0000

If you want to build a simple CRM in Notion, you don't need expensive software or a single line of code. One Notion database with a board view tracks every lead from first contact to closed deal.

What you need

A free Notion account. That's it.

Step 1: Create the Leads database

In Notion, make a new page called Leads CRM, then add a full-page database. Switch it to board view, so each stage becomes a column you can drag cards between. That board is your pipeline, and it is the view you will open every morning.

Step 2: Add six properties

Keep it simple — these six cover a real pipeline:

Property	Type
Name	Title
Company	Text
Email	Email
Deal value	Number
Next step	Text
Status	Select

Step 3: Set the status options

Set the Status select options to: New, Contacted, Meeting booked, Proposal sent, Won, Lost. Five stages are enough — too many stages just slow you down.

Step 4: Add example leads (dummy data only)

[
  { "name": "Sam Patel", "company": "Bright Studio", "deal_value": 500, "status": "New" },
  { "name": "Priya Sharma", "company": "Northwind", "status": "Contacted" },
  { "name": "Alex Chen", "company": "Harbor Labs", "status": "Meeting booked" }
]

Seeing realistic rows makes the pipeline click, and shows you exactly how a deal moves.

Step 5: Work the board

When you contact Sam, drag his card from New to Contacted. When Priya agrees to a call, move her to Meeting booked. Each drag updates the pipeline instantly, and clicking any card shows its full details and next step.

Step 6: The morning habit

Every morning, open the board and work the leftmost columns first. New leads get contacted, contacted leads get a meeting, and every card needs a next step written on it. A lead without a next step is a lead about to stall, so never leave that field blank.

Two useful views

Table view sorted by deal value — your biggest opportunities at the top.
Filtered view showing only New and Contacted — your daily follow-up list stays short and clear.

Once this is set up, adding a new lead takes ten seconds: create a card, fill in the name and company, set the status to New, and write the next step.

Watch the full tutorial above. New automation tutorial every day on the StackScale YouTube channel.

Automate Lead Tracking with Zapier: Google Forms to Sheets & Slack (No Code)

Stackscale — Sat, 07 Nov 2026 05:19:00 +0000

If you want to automate lead tracking with Zapier, one Zap replaces the entire copy-paste routine. Every Google Forms response lands in Google Sheets and pings Slack automatically, with no code at all.

What you need

A Google Form with Name, Email, Company, and Message fields
A Google Sheet with matching columns plus a Date column
A Slack channel for leads — call it #leads
A free Zapier account

Official links: Zapier · Google Forms · Google Sheets · Slack

How the Zap works

Trigger: Google Forms New Response in Form. Action 1: Google Sheets Create Spreadsheet Row. Action 2: Slack Send Channel Message. One submission, three places updated.

Step 1: Create the trigger

In Zapier, click Create Zap. Search for Google Forms and choose New Response in Form. Connect your Google account, select your lead form, and test it so Zapier can see a sample response — that sample makes the next steps easy.

Step 2: Add a row to Google Sheets

Search for Google Sheets and choose Create Spreadsheet Row. Pick your leads sheet, then map each column to the matching form field:

Sheet column	Form field
Name	Name
Email	Email
Company	Company
Message	Message
Date	Submission date

Select each field from the form data — never type values by hand, so every new lead fills itself in correctly.

Step 3: Post the Slack alert

Search for Slack and choose Send Channel Message. Pick your #leads channel and write a short alert:

New lead: {Name} — {Company} — {Email}

Keep it short. Your team should understand the lead in one glance, without opening the sheet.

Step 4: Test it with a dummy lead

Click Test Zap, then submit a test lead through your own form. Use dummy details only — never a real customer:

{
  "name": "Alex Carter",
  "email": "alex@example.com",
  "company": "Northwind Studio",
  "message": "Interested in your automation service."
}

Within seconds, check the sheet: a new row should appear, perfectly filled in. Then check Slack: your alert should be waiting in #leads. If a field is blank, go back and check your mapping — that fixes almost every error.

Step 5: Publish the Zap

Publish your Zap and turn it on. From now on, every form submission is logged and announced automatically. Your sheet becomes your single source of truth for leads, and your team hears about each one the moment it arrives.

Reuse this pattern anywhere

Job applications, support requests, event sign-ups, client onboarding — just change the form and the sheet.

Watch the full tutorial above. New automation tutorial every day on the StackScale YouTube channel.

Automate Google Forms to Notion & Slack in 5 Minutes (No Code)

Stackscale — Sat, 07 Nov 2026 05:18:44 +0000

Every lead that fills out your form should save itself — if you want to automate Google Forms to Notion and Slack, you can build the whole workflow in Make in about five minutes, with no code at all. One scenario watches your form, files each response in Notion, and alerts your team on Slack the moment it arrives.

What you need

A Google Form with Name, Email, Company, and Message fields
A free Make account
A Notion database called Leads
A Slack workspace with a #leads channel

Disclosure: Some links below are affiliate links, meaning StackScale may earn a commission at no extra cost to you.

Get started with Make here: https://www.make.com/en/register?pc=stackscale&affiliateSource=devto

The workflow at a glance

Google Forms → Make → Notion + Slack. One submission, three places updated, zero manual work.

Step 1: Create the Make scenario

In Make, click Create a new scenario. Search for Google Forms, choose Watch Responses, connect your Google account, and select your lead form.

Step 2: Save every lead to Notion

Add a Notion module and choose Create a Database Item. Connect Notion, select your Leads database, then map the fields:

Google Form field	Notion property
Name	Name
Email	Email
Company	Company
Message	Notes

Map by clicking each field and selecting it from the form data — never type values by hand, or the mapping will not update per submission.

Step 3: Alert Slack instantly

Add a Slack module and choose Post a Message. Pick your #leads channel and write:

New lead: {Name} — {Company} — {Email}

Your team sees every lead in one glance, without opening anything else.

Step 4: Test it with a dummy lead

Click Run Once, then submit a test lead yourself. Use dummy details only — never a real customer:

{
  "name": "Alex Carter",
  "email": "alex@example.com",
  "company": "Northwind Studio",
  "message": "Looking for a demo of your automation service."
}

Within seconds, the lead appears in Notion, perfectly formatted, and Slack lights up with the alert.

Step 5: Switch it on

If a field comes through blank, check your mapping — that fixes about 90% of errors. Once the test works, turn the scenario on and set it to run immediately.

Reuse it for anything

This exact workflow also handles support tickets, job applications, and client onboarding. Just change the form and the database.

Watch the full tutorial above. New automation tutorial every day on the StackScale YouTube channel.