Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Cross-Tool Workflows

Gateway's real power shows when you work across Linear, Notion, and Slack in a single conversation.

Create an Issue → Discuss → Document

You: 
Create a Linear issue for "Migrate auth to OAuth 2.1" on the platform team,
post it in #engineering for discussion, and create a Notion spec page for it
AI responds:

Done! Here's what I set up:

  • ✅ Created [PLAT-77] Migrate auth to OAuth 2.1 in Linear (platform team, backlog)
  • ✅ Posted in #engineering: "New issue: Migrate auth to OAuth 2.1 — [link to PLAT-77]. Thread for discussion 👇"
  • ✅ Created Notion page: "OAuth 2.1 Migration Spec" with a link back to the issue

The spec page has a template ready for you to fill in. Want me to add an outline?

Triage Support → Create Bugs

You: 
Search Slack #support for messages about the login error this week,
then create a Linear issue summarizing the reports
AI responds:

Found 7 messages in #support about login errors this week. Common themes:

  • 4 reports: "Login hangs for 30+ seconds then times out"
  • 2 reports: "Password reset email never arrives"
  • 1 report: "SSO redirect loops on Safari"

Created [ENG-162] Login timeout + auth issues (7 support reports) with all details and Slack message links. Assigned to triage. Want me to post a status update in #support?

Check Progress → Post Update

You: 
Check the Q1 OKRs database in Notion and post a progress summary in #leadership
AI responds:

Pulled Q1 OKR data from Notion. Posted this update in #leadership:

📊 Q1 OKR Progress — Week 11

  • Revenue: 87% of target (on track)
  • User growth: 112% of target ✅
  • API v2 launch: 60% complete (at risk — blocked on auth migration)
  • Customer NPS: 72 → 78 (improving)

3 of 5 key results on track. API v2 needs attention.

Sprint Summary → Standup Post

You: 
What's in the current engineering sprint? Post a summary in #engineering-standup
AI responds:

Current sprint ends Tuesday. Posted to #engineering-standup:

Sprint 14 — Day 8 of 10 ✅ Done (6): ENG-142, ENG-145, ENG-148, ENG-150, ENG-151, PROD-90 🔄 In Progress (3): ENG-156, ENG-160, ENG-161 ⚠️ Blocked (1): ENG-153 — waiting on DevOps 📊 Velocity: 24/31 points complete (77%)

Research → Action Items

You: 
Find the competitive analysis doc in Notion, pull out the action items,
and create Linear issues for each one
AI responds:

Found "Competitive Analysis — March 2026" in Notion. Extracted 4 action items and created issues:

  1. [PROD-95] "Add SSO support — competitor parity" (Product team)
  2. [ENG-163] "Improve search latency to < 200ms" (Engineering team)
  3. [MKT-48] "Publish comparison landing page" (Marketing team)
  4. [PROD-96] "Evaluate AI summarization feature" (Product team)

All linked back to the Notion analysis doc. Want me to assign them?

Tips

  • Be explicit about the sequence — "First search..., then create..., then post..." gives clear results
  • Name your channels and teams — "Post in #engineering" is clearer than "post in the engineering channel"
  • Reference previous results — "Use that issue link in the Slack message" carries context between steps
  • Batch when possible — "Create issues for each of these" is faster than one at a time