Rinkta + Slack: capture work and check hours from any channel | Rinkta

[Rinkta](https://rinkta.com/)

Products

Agencies

Resources

[Customers](https://rinkta.com/case-studies) [Pricing](https://rinkta.com/pricing)

[Log in](https://app.rinkta.com/session/new) [Sign up for free](https://app.rinkta.com/registration/new)

1. [Home](https://rinkta.com/)/
3. [Integrations](https://rinkta.com/integrations)

# Slack

Mention @Rinkta in any Slack thread to log billable hours or ask about workspace state. Mention-only — no background scraping, no AI training on your content.

## Overview

Mention @Rinkta in Slack to capture work or check workspace state. Nothing else gets read.

Rinkta's Slack integration is on-demand Slack time tracking for teams that already live in chat. Mention @Rinkta in a thread where work was completed and the bot reads that thread, logs a billable hour entry, and tags the right client. Mention @Rinkta with a question about hours, projects, or invoices and you get an answer in seconds. Untagged messages stay private — the bot never listens silently in the background.

## Who it's for

Any team that runs project work in Slack and bills clients by the hour. Mention @Rinkta when something ships and Rinkta picks up the pattern: standups, EOD updates, deploy notifications, design hand-offs become invoiceable time — but only the threads you tag, not your whole channel history.

For agencies running #client-acme style channels, mentioning @Rinkta on a finished deliverable lands the hours in the right Acme project. The bot answers "@Rinkta what have we billed Acme this month?" on demand, making Slack billing for agencies a one-mention setup rather than an end-of-month scramble.

For freelancers and consultants, the EOD update you already write becomes the Slack timesheet — once you @Rinkta the post. Mention what you finished and hours land against the right client. Ask "@Rinkta unbilled hours this week" before sending an invoice.

For dev teams, a deploy message tagged with @Rinkta becomes a billing entry. The bot answers @Rinkta status queries on demand, so PMs and finance leads stop tab-switching to check project hours, unbilled time, or invoice status.

## How it works

Connect Slack to Rinkta in one click. Choose your workspace, authorize the Slack bot, and Rinkta is ready to respond — but stays silent until @Rinkta is mentioned in a channel you've allowed.

When you mention @Rinkta in a thread where work was completed, AI reads that thread to understand what got done and which project it belongs to. It calculates a time estimate, creates a billing entry against the right client, and posts a confirmation in-thread. Untagged messages are never read or stored — only the thread you tagged is processed.

Need the current state of the workspace? Mention @Rinkta directly. "@Rinkta hours on Acme this week", "@Rinkta unbilled time on the redesign", or "@Rinkta status of the Smith invoice" — answers come back in seconds, sourced from your Rinkta data. The Slack bot reads from the same numbers your dashboard does.

Estimates come from what the tagged thread describes, not vague recollection. If one needs adjusting, change it in Rinkta. Slack time tracking only runs when you ask for it — there is no background scraping, no passive listening, no silent message log.

Map Slack channels to Rinkta projects during setup. After that, every @Rinkta mention in a mapped channel routes hours to the correct client without manual sorting. Channels you haven't mapped are invisible to the integration.

## Configure

Workspace administrators authenticate via OAuth2 in Rinkta settings. Choose your Slack workspace, approve channel permissions for the channels you want covered, and Rinkta installs the @Rinkta bot with a single Slack event subscription: app_mention.

The integration subscribes only to app_mention events. Rinkta receives a message payload when @Rinkta is tagged, reads the surrounding thread to identify completed work or answer the question, and posts a billing entry or response to the mapped Rinkta project. Untagged channel traffic never reaches the integration.

Privacy is enforced at three layers. The bot only sees threads where @Rinkta has been mentioned. OAuth scopes are limited to the channels you choose, so unmapped channels are invisible. Slack content is processed only to log hours or answer the asked question — never used for AI training, never shared with third parties.

Connect Slack channels to Rinkta projects at the workspace level. Mentioned work routes to client accounts based on these mappings, so billing entries appear the moment @Rinkta is tagged on a finished thread.

Slack

---

<dl>

<dt>Website</dt>
<dd>[https://slack.com ](https://slack.com)</dd>

<dt>Documentation</dt>
<dd>[https://api.slack.com/docs ](https://api.slack.com/docs)</dd>

</dl>

---

[Add to Rinkta](https://app.rinkta.com/registration/new)

FAQ

## Slack integration FAQ

Answers to common questions about tracking billable hours in Slack with Rinkta — including what the bot reads and what it doesn't.

<details>

<summary>

Can I track billable hours directly in Slack?

◀</summary>



Yes. Mention @Rinkta in a Slack thread where work was completed and the bot reads that thread, estimates how long the work took, and logs a billable hour entry against the right client. Rinkta only acts on threads where it's mentioned — it does not sit silently in your channels parsing every message.

</details>

---

<details>

<summary>

How does Rinkta capture work from Slack messages?

◀</summary>



By mention only. The Slack bot reads a thread when, and only when, @Rinkta is tagged in it. AI parses the surrounding thread to identify what was completed, calculates a time estimate, and creates a billing entry against the channel's mapped project. If Rinkta isn't mentioned, the message is never read, processed, or stored.

</details>

---

<details>

<summary>

Does Rinkta read every message in our Slack channels?

◀</summary>



No. Rinkta subscribes to a single Slack event — app_mention — so the integration only receives a message payload when @Rinkta has been explicitly tagged. It does not subscribe to broad message events, does not log untagged conversations, and never trains AI on your Slack content. Channels you haven't mapped are invisible to the integration entirely.

</details>

---

<details>

<summary>

Is the Slack integration a good fit for agencies and freelancers?

◀</summary>



Both. Agencies typically map per-client Slack channels (#client-acme, #client-smith) to Rinkta projects so mentioned work flows to the correct invoice. Freelancers usually map a single channel to a single client. The bot scales the same either way — and stays silent until @Rinkta is mentioned.

</details>

---

<details>

<summary>

Can I ask the Slack bot about project status or client hours?

◀</summary>



Yes. Mention @Rinkta in any allowed channel — "@Rinkta hours on Acme this month", "@Rinkta unbilled time on the redesign", "@Rinkta status of the Smith invoice" — and the bot returns answers from your Rinkta workspace in seconds. Permissions follow your Rinkta role, so anyone in Slack only sees what they can see in Rinkta.

</details>

---

<details>

<summary>

What does Rinkta do to protect Slack workspace privacy?

◀</summary>



Three things. First, Rinkta only reads threads where @Rinkta is mentioned — untagged messages are never received by the integration. Second, OAuth scopes are limited to the Slack channels you select; channels outside the mapping are invisible. Third, Slack content is processed only to log hours or answer the question asked, never used for AI training, never shared with third parties.

</details>

---

<details>

<summary>

How is this different from a manual Slack timesheet?

◀</summary>



A manual timesheet asks your team to stop, recall hours, and enter them. Rinkta's Slack integration captures hours from threads your team already writes — standups, deploy posts, EOD updates — by tagging @Rinkta on the message. Billable time is documented as it's described, not reconstructed days later, and only the threads you tag are ever read.

</details>

### Try it risk-free for a week

Here's the deal. Use it free for 7 days. If you don't save at least a couple hours or find work you should have billed, we'll refund everything. No questions, no hassle.

[Sign up for a free trial](https://rinkta.com/registrations/new)

No credit card required

[Rinkta](https://rinkta.com/)

### Product

- [Time tracking](https://rinkta.com/products/time-tracking)
- [Insights](https://rinkta.com/products/insights)
- [Invoices](https://rinkta.com/products/invoices)
- [Integrations](https://rinkta.com/integrations)
- [Pricing](https://rinkta.com/pricing)
- [MCP](https://rinkta.com/mcp)

### Solutions

- [Software agencies](https://rinkta.com/agencies/software)
- [Creative agencies](https://rinkta.com/agencies/creative)

### Resources

- [Guides](https://rinkta.com/guides)
- [Customer stories](https://rinkta.com/case-studies)
- [Profitability calculator](https://rinkta.com/resources/calculators/profitability-calculator)
- [Utilization calculator](https://rinkta.com/resources/calculators/utilization-calculator)
- [Alternatives](https://rinkta.com/alternatives)

### Company

- [About](https://rinkta.com/about)
- [Contact](https://rinkta.com/contact)
- [Security](https://rinkta.com/security)

### Follow us

- [Discord](https://rinkta.com/join/discord)
- [X / Twitter](https://x.com/rinktacom)
- [LinkedIn](https://www.linkedin.com/company/rinkta)
- [Instagram](https://www.instagram.com/rinktacom/)
- [Facebook](https://www.facebook.com/rinktacom)

---

Rinkta is developed, shaped and backed by [Primevise](https://primevise.com/?ref=rinkta)

- [Privacy Policy](https://rinkta.com/privacy-policy)
- [Terms of Service](https://rinkta.com/terms-of-service)