Outbound Campaigns Launched From One Slack Command

The situation

Starting a campaign meant finding prospects in Lusha, cleaning the list, building the campaign in Smartlead, adding the sequence, launching it and then creating a record in ClickUp - all by hand.

It was repetitive, tracking was inconsistent, and there was always a risk of emailing someone twice or someone who had unsubscribed.

What we built

A backend that runs the whole process from a single command: /outreach, with the brand to target.

• Prospecting: searches Lusha with the team’s targeting rules - job titles, departments, countries, seniority - and enriches contacts with work emails.
• Filtering: removes duplicates, unsubscribed contacts, blocked emails and blocked domains.
• Approval: posts the counts to Slack with Approve and Reject buttons. An auto mode skips this step when the team wants it to.
• Campaign: creates the Smartlead campaign, uploads the leads, copies the email sequence from an existing campaign and launches it, or leaves it as a draft.
• Record: creates the campaign task in ClickUp with brand, owner, prospect count and start date.
• Tracking: Smartlead webhooks update sent, open, click, reply, bounce and unsubscribe counts, sync them to ClickUp and notify Slack on replies.

Built to fail safely

Every request moves through a defined set of states, so a failed run resumes where it stopped: a campaign is not created twice and leads are not uploaded twice.

Slack requests and webhooks are signature-checked, duplicate webhook events are ignored, and API calls retry with backoff. Lusha credit use is tracked against a budget, with an alert when a job goes over.

The result

The team starts, approves and follows a campaign without leaving Slack. An admin console shows every workflow, its timeline and its prospects, and controls which Slack users may run the command.