Skip to content
All routines
SalesEvery weekday

Close-risk list

Find deals expected to close this month that have no recent activity or next step.

Starting request

Tell OpenTag exactly what to repeat

“Every weekday at 08:30 [timezone], find HubSpot deals due to close this month with no recent activity or next step. Post the owner, amount, and deal link in #sales.”

Use this as a starting point, then replace the example details with the sources, scope, and destination your team uses.

Shape it around your team

The example gives you a useful structure. The connections, scope, and schedule should match the way your team actually works.

  1. 1

    Connect the sources

    Connect HubSpot. OpenTag can only use the accounts and records those connections allow.

  2. 2

    Make the scope explicit

    Name the exact accounts, projects, owners, date range, and time zone that matter. Replace the example details with your team’s own.

  3. 3

    Check the first run

    Run it once, review the source links and Slack destination, then keep or adjust the every weekday timing.

Keep the same team context and find another recurring job to hand off.

View all sales
  • SalesEvery Monday

    Monday pipeline review

    List open Attio deals, flag records with no next step, and link the ones that need attention.

    • Attio
    • Slack
    Example request

    “Every Monday at 09:00 [timezone], review open deals in Attio, flag any without a next step, and post a sourced summary with links in #sales.”

    View routine
  • SalesBefore sales meetings

    Pre-call account brief

    Prepare the people, company context, and open questions before a sales meeting.

    • Google Calendar
    • Apollo
    • Slack
    Example request

    “Before each sales meeting on my Google Calendar, research the company and attendees in Apollo and send me a private Slack brief with sources and open questions.”

    View routine

Describe the job. OpenTag builds the routine.

Name what to read, the period to cover, the result you need, when it should run, and where it should go. Run it once and check the result before relying on the schedule.

  • Sources
  • Time window
  • Output
  • Schedule
  • Destination