Skip to content

Pack · Marketing agency

SEO agency pack

An SEO agency sells a long monthly retainer, because organic results build slowly.

Start the 14-day trial, then find it under Templates → Library. It installs into the client you choose, switched off, with its checklist.

Workflows
3
Steps
10
Client fills in
8
Starts
From Pipedrive, Stripe or Slack, within 5 minutes

UsesBeta

The workflows in this pack

Built for marketing agencies.

  1. 01

    Won-deal kickoff for marketing agencies

    When a deal is won, open the kickoff task, tell the team, and hand the owner the welcome to send, the same minute.

    1. Starts whenA deal is won
    2. App stepKick off the deal
    3. App stepTell the team
    4. NotifyTell the owner
  2. 02

    Failed payment recovery for marketing agencies

    When a card payment fails, send the customer a plain, kind message with the link to pay, by email and text, and tell the owner.

    1. Starts whenA payment fails
    2. EmailTell the customer, kindly
    3. BranchDo we have a mobile?
    4. IfIf yes
    5. TextAnd by text
    6. IfIf no
    7. NotifyTell the owner
  3. 03

    Request to task for marketing agencies

    Turn every request posted in the requests channel into a task in the team’s list, and reply in the channel with the link.

    1. Starts whenA message is posted in a channel
    2. AgentWrite the task
    3. App stepNamed by the agent
    4. App stepSay where it went

What each client fills in

Task list ID
The ClickUp list new-client tasks go into.
First steps
What the kickoff task says to do: the call, the access to collect, the first deliverable.
Team channel
The Slack channel that hears about it.
Owner’s email
Gets the summaries and the cases a person must handle.
Welcome message
The welcome the client gets, kept to send by hand while the deal record has no contact email.
Business name
How messages sign off.
AI model
The model the client’s key can use.
Requests channel
The Slack channel where people ask for things.

The accounts it needs

Each is the client’s own, stored encrypted and never copied between clients. Until one is added the client’s checklist shows it, and nothing runs.

  • In the client’s Pipedrive: your avatar → Personal preferences → API → copy the token.

  • In the client’s ClickUp: avatar → Settings → Apps → API Token → Generate.

  • In the client’s Slack: api.slack.com/apps → Create New App → OAuth & Permissions → add the chat:write scope (and channels:history, plus groups:history for a private channel, for the message trigger) → Install to Workspace → copy the Bot User OAuth Token. Invite the app to the channel.

  • In the client’s Stripe dashboard: Developers → API keys → Create restricted key. Give it only what the steps need: Customers write, Payment Links write, Prices read, Invoices write, and Webhook Endpoints write for the triggers. Leave “IP access” empty: Thrum has no fixed addresses, so a key locked to IPs fails every call.

  • platform.claude.com → Settings → API keys → Create key, in the workspace that bills this client.

After you install it

It lands switched off. The client’s checklist holds exactly this:

  1. Connect the client’s Pipedrive, for “A deal is won”
  2. Connect the client’s ClickUp, for “Kick off the deal”
  3. Connect the client’s Slack, for “Tell the team”
  4. Connect the client’s Resend (email), for “Tell the owner”
  5. Fill in Task list ID (The ClickUp list new-client tasks go into)
  6. Fill in First steps (What the kickoff task says to do: the call, the access to collect, the first deliverable)
  7. Fill in Team channel (The Slack channel that hears about it)
  8. Fill in Owner’s email (Gets the summaries and the cases a person must handle)
  9. Fill in Welcome message (The welcome the client gets, kept to send by hand while the deal record has no contact email)
  10. Connect the client’s Stripe, for “A payment fails”
  11. Connect the client’s Resend (email), for “Tell the customer, kindly” and “Tell the owner”
  12. Connect the client’s Twilio (SMS), for “And by text”
  13. Fill in Business name (How messages sign off)
  14. Connect the client’s Slack, for “A message is posted in a channel” and “Say where it went”
  15. Connect the client’s Anthropic, for “Write the task”
  16. Connect the client’s ClickUp
  17. Fill in Requests channel (The Slack channel where people ask for things)
  18. Fill in AI model (The model the client’s key can use)
  19. Fill in Task list ID (The ClickUp list the tasks go into)

Thrum is cooking.

Get early access and you’ll be among the first in. Early members get a launch perk.