Approve new newsletter contacts in Slack before adding them

Each day, new CRM contacts are checked for a newsletter tag, with Slack approval for anything unclear.

How the work actually flows

It branches. Exactly one path is taken; runs once per each new crm contact.

Pattern: Exclusive Choice (4) · Simple Merge (5) · Multiple Instances with a priori Run-Time Knowledge (14)

flowchart TD trig(["daily scheduled check"]):::trigtime s0["fetch new crm contacts"]:::svc s1[["check newsletter tag status"]]:::mi s2["add contact to newsletter list"]:::svc trig --> s0 s0 -->|"one per each new crm contact"| s1 gx{"× already tagged or not"}:::gate s1 --> gx p00["skip straight to adding"]:::task gx -->|"already tagged"| p00 p10["ask slack for approval"]:::task gx -->|"not tagged"| p10 p11["add once approved"]:::task p10 --> p11 jn{"○ before adding contact"}:::gate p00 --> jn p11 --> jn jn --> s2 out[/"newsletter list updated with approved contacts"/]:::out pay{{"keeps list current without daily manual checks"}}:::pay s2 --> out out --> pay classDef task fill:#e7f6fe,stroke:#34b8f0,color:#2c2a29 classDef svc fill:#f6f8fa,stroke:#7c8795,color:#2c2a29 classDef mi fill:#e7f6fe,stroke:#0079a8,color:#2c2a29,stroke-width:2px classDef human fill:#fff,stroke:#0079a8,color:#0079a8 classDef store fill:#f6f8fa,stroke:#0079a8,color:#2c2a29 classDef trig fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigtime fill:#00a4eb,stroke:#0079a8,color:#fff,font-weight:bold classDef trigdata fill:#8ad4f5,stroke:#0079a8,color:#06314c,font-weight:bold classDef gate fill:#fff,stroke:#e8a23d,color:#6b4708,font-weight:bold classDef out fill:#1f9d6b,stroke:#167a53,color:#fff,font-weight:bold classDef pay fill:#06314c,stroke:#021f33,color:#fff
Starts itAn outside serviceRuns once per itemOne path onlyPaths rejoinResultPayoff
Build size
Standard

A mid-size build with several tools working together.

Business functions
CRM & Sales PipelineEmail AutomationMessaging & NotificationsImage & Media Processing
Connects
CentralStationCRMRapidmailSlack
Featured in

The problem it solves

You want to keep your newsletter list current with new CRM contacts, but you don't want just anyone added without a quick check. Manually cross-referencing your CRM and email list every day eats into your time.

Who it fits

A small business or marketing team managing a CRM and a separate email newsletter list.

How it works

  1. Every day at a set time, the automation checks for new contacts in your CRM
  2. It checks whether each contact already has a Newsletter tag
  3. If not tagged, you get a Slack message asking whether to add them
  4. Once approved, or if already tagged, the contact is added to your newsletter list
What you get

New contacts your team actually approved

New contacts in your CRM get checked for a newsletter tag daily, and anything unclear gets a quick approval request sent to your Slack first.

What you get

An up-to-date newsletter subscriber list, with a Slack record of approvals.

What you need

A CentralStationCRM account, a Rapidmail account, and a Slack workspace.

We can build this. But should you?

The hard question is not how to build it. It is whether this is the right thing to build first.

That is what a Fractional Chief AI Officer figures out with you, before anyone writes a line of code.

Let's Talk Strategy

Related automations

Back to the AI Playbook