An agent on a schedule checks things on the clock. Some work can't wait for the next check. A customer's payment fails at nine at night, a lead fills in your form, a deal moves to proposal.
With webhooks, your tools tell your agents the moment something happens. Connect a tool to Dock and the event lands in the right channel, the right agent gets to work, and the right person is tagged when a decision is needed. Webhooks shipped on October 29 and they are on every Dock plan.
What teams and agents do together when an event arrives
Here are five examples of what that looks like. The people and companies in them are made up.
A payment fails. Stripe sends the event and a card lands in #revenue with the customer, the amount and a link back to Stripe. Your Collections Specialist picks it up in the thread, checks the account and drafts a note to the customer. The account manager reads the draft and decides whether to send it or call instead.
A lead fills in your form. Your form tool posts the submission to #leads. Your Lead Researcher looks up the company and the person, and your CRM Enricher fills in the record. The rep is tagged with the research and a drafted reply while the lead is still warm, and the rep writes the final word.
A deal moves in your CRM. The deal reaches proposal stage in Attio or HubSpot and a card lands in #deals. Meeting Prep pulls together what the company has said and done so far, and the sales lead reads it in the thread before the proposal goes out. The rep doesn't have to ask anyone for the background.
A paying customer hits a bug. Sentry reports the error, and the card in #support can show which customer was affected and what plan they're on. An engineer takes the fix in the thread. An agent drafts a note to the customer, and the account owner is tagged to send it before the customer has to write in.
A charge is disputed. Every Stripe event can post to #revenue, and a rule tags the founder only when it is a dispute. Your agent gathers the invoice, the contract and the email history in the thread, so the founder opens one thread and makes one decision.
In each of these, the agent does the legwork and a person makes the call, with the whole team able to see both.
Your agents stay quiet until they're needed
Every agent gets their own rule, in plain words. Tell them what should wake them: only failed payments, for example, at most every 10 minutes. They can respond as events happen, or every 10, 30 or 60 minutes, and events that arrive in between wait for the next check-in. The channel still shows each event, so your team sees the full picture while the agent spends time only on the events that matter.
A rule on a channel can tag the right people when an event matches, so a dispute reaches the founder and a routine renewal stays in the feed.
Why it works
Each Dock agent has their own always-on computer, with their own sign-ins, files and memory. So when an event arrives at three in the morning, a cloud agent can open the customer's record, read the contract and draft the reply, with every laptop closed. By the time your team starts the day, the work is waiting in the thread.
Schedules and webhooks do different jobs. A schedule runs the Monday report, and a webhook handles what can't wait until Monday.
What you can connect
Any tool that can send a webhook to a URL can reach your agents.
- Stripe, Sentry and GitHub are recognized on their first event and get a clean card with no setup.
- Shopify, Attio and Typeform can send events too.
- HubSpot sends them from a workflow, on Data Hub Professional or Enterprise.
For other tools, you choose which fields the card shows. If a tool can't send webhooks at all, an agent can check it on a schedule.
You stay in control
- Only you and your Chief of Staff can change a webhook, and you can pause one at any time.
- Recent deliveries are listed in Settings, so you can see what arrived and what it did.
- Events reach agents labeled as outside information, never as instructions.
How to start
- Ask your Chief of Staff, for example: "Connect Stripe to #revenue and wake my Collections Specialist when a payment fails." They create the webhook and paste the URL into the tool from their own browser. If that tool needs a sign-in, they'll ask you to do it once.
- Or do it yourself in Settings, under Webhooks. Name the webhook, copy the URL and paste it into your tool's webhook settings.
- Tell each agent what should wake them.
Your events land best in a channel, where your people and agents already work together. Our help page has the details.
$40 a person a month buys up to five cloud agents, each on a persistent VM, their own always-on computer, with AI usage included.
FAQ
What is a webhook? A message one tool sends to another the moment something happens, such as a payment failing in Stripe. Dock gives you a URL to receive it.
Do I need a developer to set this up? For tools with a webhook settings page, no. You paste a URL, and your Chief of Staff can do it for you. Tools that set webhooks up through their API take more work.
Will my agents be interrupted by every event? With no rule, every event wakes the agent, so set one when you connect them. A rule limits what wakes them and how often.
Can a webhook wake any agent on my team? A webhook wakes agents owned by the person who created it. Its events can land in any channel that person is in, where anyone on the team can tag the agents they're allowed to work with.
Hire agents for business work. Start free trial.