Skip to content

Unofficial community registry. Not affiliated with, endorsed by, or sponsored by xAI.

中文

Routines

Deals that have gone quiet

quiet-deals

List open deals with no update for the number of days you set, or with no next step. Read only. Do not change the stage or send mail.

for Grok Bot · unofficial, not affiliated with xAI

CNPS0.1.02026-11-18New

Paste this into Grok Bot and say: create this routine.

Create this routine: Deals that have gone quiet

Trigger: Monday, list open deals with no update for the number of days you set, or with no next step.

What to do:
1. Filters by a number of days you set, such as 14 days without an update.
2. Flags records with no next-step date.
3. Writes a list. It does not edit CRM fields.

How:
1. Write the stage names and the number of days. Do not reuse an example stage name from another team.
2. Keep the connector read-only.
3. Run it once and check three rows against the CRM.
4. When you want a letter, use From a lead to a first-email draft, one lead at a time.

Rules you can keep:
Read open deals from the read-only CRM.
Keep rows where the last update is older than N days, or the next step date is empty. The user sets N at the top of the routine.
Output: name, owner, last update, amount if that field exists.
If a field is missing, write "no such field". Do not estimate an amount.
Write outputs/quiet-deals.md.
Do not change stages, do not create activities, do not send mail.

Do not:
- Do not post a list of customer names and amounts to a public channel.
- Do not keep using this routine if the connected app can write.
- Do not send chase mail from the list, and do not change a deal stage.

Paste this into Grok Bot and say: create this routine.

What it does

  • Filters by a number of days you set, such as 14 days without an update.
  • Flags records with no next-step date.
  • Writes a list. It does not edit CRM fields.

Who it is for

Sales leads who want a Monday list of stalled deals.

How to put it in Grok Bot

  1. Write the stage names and the number of days. Do not reuse an example stage name from another team.
  2. Keep the connector read-only.
  3. Run it once and check three rows against the CRM.
  4. When you want a letter, use From a lead to a first-email draft, one lead at a time.

Example

Routine snippet

Read open deals from the read-only CRM.
Keep rows where the last update is older than N days, or the next step date is empty. The user sets N at the top of the routine.
Output: name, owner, last update, amount if that field exists.
If a field is missing, write "no such field". Do not estimate an amount.
Write outputs/quiet-deals.md.
Do not change stages, do not create activities, do not send mail.

Connectors it needs

Safety and permissions

  • Do not post a list of customer names and amounts to a public channel.
  • Do not keep using this routine if the connected app can write.
  • Do not send chase mail from the list, and do not change a deal stage.

Risk: Medium

Questions

The amount is empty. Can it guess from the industry?

No. Empty stays empty.

The owner has left.

Write the name that is in the field. Do not reassign inside the routine.