> For the complete documentation index, see [llms.txt](https://help.rhythms.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.rhythms.ai/getting-started/getting-started-in-slack/how-to-check-in-on-your-goals-from-slack.md). # How to check in on your goals from Slack Check-ins are the thing everyone means to do and nobody remembers. The fix isn't discipline — it's doing them where you already are, in the words you'd use anyway. **The short answer** In any channel Rhythms is in, post `@Rhythms check in on my goals` and reply the way you'd tell a teammate what happened. Rhythms converts it into a check-in on the right goal and shows you the draft. **Nothing saves until you confirm.** *** ## Before you start * [**Setup Rhythms in Slack**](/getting-started/getting-started-in-slack/getting-started-with-rhythms-in-slack.md) * **Have at least one published goal:** Learn how to setup and [manage goals in Slack](/getting-started/getting-started-in-slack/how-to-manage-goals-from-slack.md) * **Start a check-in rhythm**, if you want to be prompted rather than remember *** ## Step 1: Tell it what's true ## If you know which goal Name it, and say what happened. **Try it:** `@Rhythms check in on my goals` > **Also works:** *"update my Q3 revenue goal, we closed the two enterprise deals" · "mark the onboarding project 80% done" · "we're behind on activation, put it at risk"* ## If you'd rather it prompt you Ask what's due, and it comes back with the list. **Try it:** `@Rhythms what check-ins are due this week?` > **Also works:** "what haven't I updated in a while?" · "which of my goals are overdue for a check-in?" **Tip: Connect the apps behind your goals** Rhythms can then suggest the check-in from what actually changed, instead of asking you to remember it. [Set up a connector →](/connectivity/connectors/set-up-automatic-updates-from-a-connector.md) ## If you have check-in notifications enabled on Slack Reply to the notification with your check-in updates. Rhythms updates it without you having to leave Slack. ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-179b0dee06b1c69f59509ba82eebdd142f8e3ce4%2F1787581117287-CheckinNotification-edited.png?alt=media) *** ## Step 2 : Optional · Turn a conversation into a check-in A lot of progress gets talked through in a channel before anyone logs it: a thread about how the migration's going, a quick "*where are we on renewals*" back-and-forth. Tag Rhythms once that conversation exists and it turns the discussion itself into check-in drafts. ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-352045a7c12bf83462c2d7e5d148ee273dd8917f%2F1787581287421-Checkinfromthreadcopy.png?alt=media) **Try it:** `@Rhythms turn this conversation into check-ins` > **Also works:** "did we cover anything check-in worthy in here?" · "log what we just decided against the right goals" It only pulls from what was actually said. If the thread doesn't clearly cover a goal, it leaves that one out rather than guessing. This also handles **several goals at once** — either ask directly, or let one conversation that touched four goals become four drafts you approve together. *** ## Step 3: Review the draft, then confirm Rhythms shows you what it's about to log against the goal, and where the number or status is coming from. ![](https://4039886202-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FEGNgNGJOnocLzqT0TwtU%2Fuploads%2Fgit-blob-ecbd34089c596035c3d3ce53960849b46c4284d4%2F1787579905998-image.png?alt=media) **Every check-in is a draft until you confirm it.** Reply in the thread to correct anything before it saves — that's faster than starting over. **Try it:** `@Rhythms make it 65% and note the API delay` > **Also works:** "actually mark it at risk" · "change the note to mention the vendor delay" · "wrong goal — I meant the activation one" Disagreeing with a suggested status is normal and cheap. Say so in the thread and it updates the same draft rather than making you begin again. **Where the draft comes from:** what you said in the thread, plus any connectors you have set up. When it isn't sure, it asks rather than guesses. *** ## Make it a habit **Get asked, instead of remembering.** Once your check-in rhythm is set, Rhythms can prompt you in the channel or in a DM when one is due. **Try it:** `@Rhythms remind me when my goals are due for a check-in` **Ask before you update.** Not sure what's changed since last time? **Try it:** `@Rhythms what's changed on my goals since my last check-in?` > **Also works:** "what did I say last time on this goal?" · "has anything moved on my goals this week?" *** ## Worth knowing **This is the same check-in as the web app.** Not a Slack-only shadow copy. Anything logged here shows up on the goal in the product, and vice versa. **In a DM you don't need to tag it.** Just talk to it. The `@Rhythms` prefix is only for channels and threads. *** ## If something didn't work It picked the wrong goal Say so in the thread — "wrong goal, I meant the activation one." It'll redraft against the right one. Naming the goal explicitly in your first message avoids this when you own several similar ones. It says it can't find a goal to check in on Either you have no published goals, or the ones you have are still drafts. Drafts are invisible to check-ins. It won't accept a number That goal has no metric — check in with a status and a note instead, or add a metric to the goal. Nothing happened when I tagged it Rhythms isn't in that channel. Add it, or check in from a DM. *** ## Try Next * [**Manage goals from Slack →**](/getting-started/getting-started-in-slack/how-to-manage-goals-from-slack.md)When the goal itself needs to change, not just its status * [**Work on documents from Slack →**](/getting-started/getting-started-in-slack/how-to-work-on-documents-from-slack.md) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.rhythms.ai/getting-started/getting-started-in-slack/how-to-check-in-on-your-goals-from-slack.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.