--- title: "Slack" description: "7 posts about Slack, summarised, each linking to the original." --- # Slack > 7 posts about Slack, summarised, each linking to the original. ## Articles ### [Run recurring jobs on Stripe without a cron server](https://yomu.fyi/post/run-recurring-jobs-on-stripe-without-a-cron-server.md) - Company: [Stripe](https://yomu.fyi/company/stripe.md) - Author: Tanya Boiteau - Published: Oct 13, 2026 - Type: Announcement Stripe Workflows now supports recurring schedule triggers, enabling automated tasks like notifying teams about past-due subscriptions without external cron servers. Users set schedules in the Dashboard, and Stripe runs the workflow at each scheduled time, following the local clock and handling daylight saving time. A walkthrough lists past-due subscriptions, uses a metadata key condition to skip already-notified ones, and sends Slack notifications via the installed Slack app. The workflow handles pagination; if an action fails, the loop stops and remaining items are picked up on the next run, with details showing which step failed. This eliminates the need for a separate server, secret key storage, and daylight saving time logic, putting calendar-based operations under the finance team’s control. ### [Automating Twilio Auth Token Detection and Rotation with TruffleHog, Tines, and Slack](https://yomu.fyi/post/automating-twilio-auth-token-detection-and-rotation-with-trufflehog-ti.md) - Company: [Twilio](https://yomu.fyi/company/twilio.md) - Author: Matt Coser - Published: Sep 21, 2026 - Type: Tutorial Hardcoding Twilio Auth Tokens in source code or exposing them in plaintext leaves communication systems vulnerable to account takeover, toll fraud, and unauthorized exploitation. This tutorial presents an automated detection and rotation pipeline using TruffleHog for secret scanning, Tines for security workflow automation, and Slack for user interaction. TruffleHog scans local directories or remote Git repositories for Twilio secrets, performs live verification via API requests, and outputs results in JSON. Tines ingests detection events through a webhook, parses the results, and triggers a Slack notification with interactive buttons for acknowledgment, scheduling remediation, or immediate rotation. Upon rotation, Tines calls the Twilio Account API to generate a new secondary auth token, displays it in a Slack modal for secure copy, and eventually promotes it to primary, while the old token is revoked. ### [Salesforce and Anthropic expand partnership](https://yomu.fyi/post/salesforce-and-anthropic-expand-partnership.md) - Company: [Anthropic](https://yomu.fyi/company/anthropic.md) - Published: Sep 10, 2026 - Type: Announcement Salesforce and Anthropic announced an expanded partnership making Claude a preferred model for Salesforce’s Agentforce platform, with availability aimed at customers in regulated sectors including financial services, healthcare, cybersecurity, and life sciences. Through Amazon Bedrock, Claude traffic will remain within Salesforce’s virtual private cloud and trusted environment, while industry-specific solutions are being developed beginning with financial services. The companies are also deepening Claude’s Slack integration through a Model Context Protocol server that can access channels, messages, and files for summaries, decisions, drafts, searches, and connected Salesforce CRM and Tableau insights. Salesforce is deploying Claude Code across its global engineering organization, and Anthropic uses Claude in Slack for internal sales workflows. Agentforce powered by Anthropic and the Claude-Slack bidirectional integrations are available today, while the regulated industry collaboration and Agentforce 360 integration for Claude remain under development. ### [How We Made All Swiggy Apps Operations AI-Native](https://yomu.fyi/post/how-we-made-all-swiggy-apps-operations-ai-native.md) - Company: [Swiggy](https://yomu.fyi/company/swiggy.md) - Author: Raj Gohil - Published: Jul 17, 2026 - Type: Explainer Swiggy’s mobile engineering teams faced operational overload as releases, production signals, and reviews required switching among Jira, Confluence, Bitrise, Play Console, Crashlytics, New Relic, Google Sheets, ImageKit, and Slack. The response was an operating layer built around Slack-native agent workflows, reusable AI skills, MCPs, and scheduled jobs connected to release, observability, QA, cost, and internal mobile systems. It can generate readiness updates, group Jira work, identify missing owners and blockers, summarize vitals, analyze alerts, follow up TRM actions, and recommend RAMP, HOLD, or ROLLBACK for staged rollouts by correlating Crashlytics, Play Vitals, and adoption. Humans still approve rollout actions, while recurring channel reports make observability and accountability more consistent and reduce clerical integration work. The stated model lets agents handle mechanical load while engineers retain judgement, ownership, product quality, architecture, and execution. ### [Improvements to Cursor in Slack](https://yomu.fyi/post/improvements-to-cursor-in-slack.md) - Company: [Cursor](https://yomu.fyi/company/cursor.md) - Published: Jul 17, 2026 - Type: Announcement Cursor in Slack now gives users more control over tasks by presenting a plan before work begins and reporting status as it progresses. Its Slack presentation has also changed: compact footer links replace in-message buttons, while tables, pull requests, and artifacts render more cleanly. In named multi-repo environments, Cursor can select an environment with access to related frontend, backend, and shared-code repositories; if it needs another repository, it prompts for a switch and resumes the task afterward. Cross-channel workflows let Cursor read context from other channels and threads and send updates to the original thread or a relevant channel. Together, these changes support earlier redirection, broader repository access, and task coordination across Slack workspace conversations. ### [Introducing Claude Tag](https://yomu.fyi/post/introducing-claude-tag.md) - Company: [Anthropic](https://yomu.fyi/company/anthropic.md) - Published: Jul 15, 2026 - Type: Announcement Claude Tag is a Slack-based way for teams to delegate work to Claude by tagging @Claude in shared channels, with access to selected tools, data, and codebases. Claude breaks requests into stages, uses permitted tools, replies in threads, retains relevant channel context, and can pursue scheduled tasks asynchronously; ambient behavior can also surface information and follow up on unresolved work. Administrators scope Claude identities, memories, tools, and information by channel, set organization- and channel-level token-spend limits, and review activity logs, while users can also message Claude privately. Available in beta to Claude Enterprise and Team customers, Claude Tag replaces the existing Claude in Slack app, works with Opus 4.8, and is credited with creating 65% of the product team’s code through Anthropic’s internal version. ### [Implementing ChatOps into our Incident Management Procedure](https://yomu.fyi/post/implementing-chatops-into-our-incident-management-procedure.md) - Company: [Shopify](https://yomu.fyi/company/shopify.md) - Author: Daniella Niyonkuru - Published: Feb 13, 2018 - Type: Explainer Shopify’s incident management process separates coordination from technical remediation: the incident manager on call (IMOC) leads response, while component experts fix production issues and a Support Response Manager handles public communication. The process follows a simplified Incident Command System hierarchy and moves from detection and confirmation through communication, mitigation, verification, documentation, investigation, and root cause analysis. Its ChatOps chatbot, Spy, runs in Slack through Lita and integrates with PagerDuty, StatusPage, and GitHub via webhooks, providing commands for paging, incident startup, status communication, mitigation, and stopping incidents. Spy binds incidents to a shared #war-room, records notes and event times, generates service disruption documents, sends status-page reminders, and can summon the IMOC squad when an incident lasts beyond a specified period. The result is a more consistent response that reduces context switching and post-incident toil while supporting detailed post-mortems.