MVP & Special Mention Slack Automation

Problem

Recognition messages for MVPs and special mentions needed to be posted to Slack at the right time without manual scheduling. The source inventory confirms a screenshot-based Zapier workflow that started from a Google Sheets recognition response, found the Slack user, checked a Friday 11:00 AM ET timing rule, delayed when needed, and posted a private Slack channel message.

Because this source is screenshot-based, exact Zapier step names and safe recognition fields are not fully confirmed.

Objectives

Start from a new recognition response stored in Google Sheets
Use Zapier to process the response
Find the Slack user based on the submitted recipient email
Decide whether the current time is before Friday 11:00 AM ET
Delay until Friday 11:00 AM ET when needed
Post the recognition message to a private Slack channel
Keep recipient details, private channel names, and recognition fields public-safe

Solution

The Zapier workflow connected the recognition response source to Slack delivery. A form response was stored in Google Sheets, Zapier picked up the new response, looked up the Slack user, evaluated the scheduled recognition time, and either delayed until Friday 11:00 AM ET or sent the message immediately.

The portfolio version describes the flow at a system level because the available source is screenshot-based rather than a full exported automation file.

Architecture

The confirmed architecture is a form to Google Sheets to Zapier to Slack notification flow. The normalized workflow data represents a recognition form, Google Sheets response, Zapier trigger, Slack user lookup, schedule decision, optional delay, and private Slack message.

Recognition Message Scheduling Flow

1
Recognition formTrigger
A recognition response captures MVP or special mention details.
2
Google Sheets responseAction
The response is stored in Google Sheets.
3
Zapier triggerAction
A new recognition response starts the Zap.
4
Find Slack userAction
The recipient is resolved in Slack using the submitted email address.
5
Before Friday 11:00 AM ET?Decision
Zapier decides whether to delay or send immediately.
6
Post private Slack messageOutput
The recognition message is posted after the delay or immediately when the scheduled time has already passed.

Workflow

A recognition form submission is stored in Google Sheets.
Zapier starts from the new recognition response.
The workflow looks up the Slack user by the submitted recipient email.
Zapier checks whether the current time is before Friday 11:00 AM ET.
If it is before that window, Zapier delays until Friday 11:00 AM ET.
Otherwise, the workflow sends immediately.
The recognition message is posted to a private Slack channel.

Tools Used

Zapier - trigger, lookup, decision, delay, and message orchestration
Google Sheets - recognition response source
Slack - user lookup and private channel message destination

Technical Decisions

Screenshot-based reconstruction: The source inventory confirms this workflow from screenshots, not a full exported source file. Exact internal Zapier step names should remain generalized.

Scheduled delivery rule: The workflow uses a Friday 11:00 AM ET timing rule. The inventory notes that whether the delay is absolute scheduled time or relative delay needs confirmation.

Slack user lookup: The workflow resolves a Slack user before posting, but the exact lookup step name and message configuration are not confirmed.

Challenges Solved

Scheduled recognition: Messages could be prepared before the recognition window and posted at the intended time.
Recipient resolution: The workflow looked up the Slack user from the response data.
Conditional timing: The workflow chose between delaying and sending immediately.
Public-safe documentation: Recognition fields, channel names, recipient details, and message content must stay generalized.

Results

The confirmed output was a Slack private channel message for the recognition workflow.

Metrics such as volume of recognition messages, manual time saved, or delivery reliability are not confirmed from the screenshot-based inventory.

Future Improvements

Generalized: confirm the exact Google Sheets trigger event name from the Zapier screenshot.
Generalized: confirm the exact Slack lookup and message step names.
Generalized: verify whether the delay is absolute scheduled time or relative delay.
Generalized: approve which recognition fields are safe to describe publicly.

Lessons Learned

Generalized: screenshot-based automations can still be documented, but the case study should clearly separate confirmed workflow behavior from details that need confirmation.

The confirmed value of the workflow is the scheduling pattern: response captured, recipient resolved, timing checked, and Slack message posted at the correct recognition window.

If I Rebuilt This Today

Generalized: I would export or document the Zapier step configuration in a sanitized format so the case study could reference exact step names without relying on screenshots.

I would also define a public-safe field list before adding examples of recognition message content.

Engineering Notes

Confirmed source type: screenshot-based.
Confirmed trigger pattern: Google Sheets new recognition response.
Confirmed timing rule: before Friday 11:00 AM ET, delay until Friday 11:00 AM ET; otherwise send immediately.
Unconfirmed: exact Zapier step names, exact Slack lookup and message step names, delay type, and public-safe recognition fields.