Skip to content
TulipFarm

Usage digest agentSee use rise and fall at a glance.

Every Friday it reads your usage sheet and writes a short digest: who is growing, who is flat and who is falling off. Your team reads it in Slack.

Your first signup includes $50 in free credits.

Fridays · 15:00

Send a weekly usage digest

Reads
Usage sheet
Grows
A weekly digest
Lands in
Slack
Google SheetsSlack
Send a weekly usage digest: starts Fridays · 15:00, uses Google Sheets, Slack.

Ask for it once, in plain words.

No flowchart to draw. Describe the job in chat. TulipFarm sets up the agent and its workflow, and shows you both before anything runs.

You

Every Friday at 3pm, read my usage sheet and post a digest to #success: customers whose use grew, stayed flat or dropped.

TulipFarm

I made an agent called Usage digest and a Friday 15:00 schedule. It reads your usage sheet. Posting to Slack asks you first. Activate it?

ActivateEdit first

One Friday, start to finish.

Every run is saved as an agent task you can open, check and rerun.

  1. Schedule

    Fridays at 15:00

    Run startedStarted
  2. Reads

    This week's and last week's usage in Google Sheets

    30 accounts
  3. Checks

    Which accounts rose or fell by more than 20 percent?

    4 up, 3 down
  4. Writes

    A short digest with the biggest moves

    1 digest
  5. Asks first

    Post the digest to #success

    Approved
  6. Posts

    Message in Slack

    Delivered 15:02Completed

What lands in #success.

Winners first, then the accounts to call.

What gets planted.

Three parts you own and can change at any time.

  1. Agent

    Usage digest

    What counts as a big move.

  2. Table

    Usage

    One row per customer per week.

  3. Workflow

    Fridays 15:00

    Runs with your own access.

Uses

  • Google SheetsGoogle Sheets
  • SlackSlack

Add if you use it

  • PostgresMCPPostgres
  • GmailGmail
  • HubSpotHubSpot

It reads quietly. It asks before it acts.

Reads without asking

  • Your usage sheet or table
  • Last week's numbers
  • Your threshold for a big move

Asks you first

  • Posting to Slack

It uses your own connections, so it never sees more than you can.

Grow it your way.

  • Pull from the database

    Read usage straight from Postgres through a Custom MCP connection.

  • One note per owner

    Send each account owner only their own accounts.

  • Add a draft

    Draft a check-in email for each falling account.

Questions, answered.

Where does the usage data come from?

From a sheet or table you keep up to date. A database such as Postgres can feed it through a Custom MCP connection, and you review each tool first.

Does it send anything to customers?

No. The digest goes to your team. Any email it drafts for a customer asks you first.

Can I change the threshold?

Yes. Say it in plain words, such as 10 percent, and the next run uses it.

Friday: who needs a call.

Public beta, open to everyone. Your first signup includes $50 in free credits.