Explore use cases
Ready-to-run playbooks for every team. Pick your team, copy the setup, and have Hops working in your Space today.
Most use cases start with a question. Connect the apps Hops needs, then copy a prompt from the page and ask. Add a skill when you want Hops to follow the same format every time, and an automation when you want it to run without being asked. Pick the team closest to yours and start from there.
Start here
Browse by team
Leadership
Go-to-market
Product & Engineering
Back office
Services
How every use case is built
Every use case page has copyable prompts, the connections it needs, and only the setup steps that apply. You build up in this order, and stop as soon as you have what you need.
Each page opens with a How it runs note that tells you which of these it uses:
- Ask Hops: ask in chat whenever you need it. No skill or automation.
- Ask Hops + skill: ask in chat, with a skill that keeps the output consistent.
- Scheduled: an automation runs on a schedule, posts an alert to Slack or the Space, and saves a Doc or Table.
- Triggered: an automation runs when something happens, like a new deal, ticket or form.
- Space per client or deal: one Space per account, project or deal, with its own context and automations.
New to Hops?
Start with the Quickstart to create your first Space, then come back and pick a use case.