Skip to guide
GrowthubDocsOpen Growthub

Triggers and follow-ups

Delegate a future follow-up, let the current turn finish and receive the result in the same conversation.

Illustrated example, not an exact screenshot. Enlarge for the details; follow the current instructions below for the controls in your account.

Explore this guide

Arrange a follow-up naturally

Use Growthub Triggers in an ordinary conversation with your selected Claude or Codex account. Tell your Character what to check, when to return and what counts as finished. It saves the follow-up and can finish its current turn.

Example request
In 15 minutes, check the selected task using my connected Asana account. Save a short update in this conversation with a link to the task. Then turn off this one-time follow-up.
Read the full section

Arrange a follow-up naturally

Use Growthub Triggers in an ordinary conversation with your selected Claude or Codex account. Tell your Character what to check, when to return and what counts as finished. It saves the follow-up and can finish its current turn.

Waiting consumes no active model turn. The follow-up stays with the same Growthub conversation; it does not create a recurring Routine. The next turn respects your saved provider selection, current access and tool permissions.

Example request · adapt to your work
In 15 minutes, check the selected task using my connected Asana account. Save a short update in this conversation with a link to the task. Then turn off this one-time follow-up.

Be specific about connected work

Name the exact connected account and resource, such as a task, email thread or Slack conversation. Your agent can arrange supported event-driven follow-ups using its available tools. It must confirm the actual source setup; having a connector installed does not mean every service provides an automatic event subscription.

A timed follow-up can check current source state when it returns. For a watch, specify the selected event, expiry and when to stop. A source event supplies information and never answers a permission request on your behalf.

Return to the same conversation

When due, the follow-up starts ordinary work in the original thread through your selected provider and permitted connectors. Open that conversation to read the saved reply and source links.

A compatible executor and the selected connected account must be available. If the thread is already busy or needs your input, the pending follow-up keeps its identity rather than starting a competing turn or bypassing the question. Reopening the page does not create another follow-up.

Turn a future follow-up off

Waiting, Finished and Cancelled describe different states. Cancelling a future trigger does not stop an already admitted turn; use the conversation’s normal Stop control for active work. It does not pause your Routines.

  1. Ask in the same conversation, or open Profile Settings → Triggers.
  2. Find the follow-up by its objective and time. Open conversation takes you to its original thread.
  3. Select Cancel follow-up to prevent a future wake. Refresh to read its current state.
Example request · adapt to your work
Turn off this conversation’s future wake-up trigger. Confirm which follow-up was cancelled.

Keep going