Town's documentation describes an assistant that connects email, calendar, documents, and other applications, then uses Tasks, Need to Know, routines, and approvals to turn context into follow-through. Its integration directory spans productivity, communication, CRM, project management, finance, meetings, data, and custom MCP tools. That range is useful—but it also makes scope the most important design decision.
How to build a useful Town routine
| Routine | Useful integrations | Good output |
|---|---|---|
| Morning briefing | Calendar, email, selected news or company sources | A short summary of what changed and what deserves attention. |
| Sales follow-up | CRM, recent messages, account or market updates | Prioritized accounts and drafts ready for review. |
| Project review | Project tool, documents, issue tracker | Blocked work, owners, decisions, and next actions. |
| Finance workflow | A narrow transaction or reporting system | A prepared report or proposed action with stronger approval controls. |
Fewer tools usually make the result easier to explain. If a connection does not change the routine's decision or output, leave it out.
Example: a Friday prospect routine
Consider a routine that says: “Review this week's prospect replies, find accounts with a material company update, and draft follow-ups for my approval.”
- Email and CRM establish the work queue.
- A maintained source feed supplies the account or market update.
- Town assembles the evidence and drafts the follow-up.
- The owner reviews the source and draft before anything is sent or written back.
That is more useful than giving the routine every available integration and asking it to “help with sales.” The trigger, inputs, output, and approval point are all visible.
Keep information and action separate
A routine can read a current update and prepare a task without being allowed to send a message, edit a CRM record, or trigger a transaction. Town's custom-routine guidance is a useful starting point for thinking about that boundary. Read access supplies evidence; approval controls govern what happens next.
Where Synorb fits
Synorb is making this recommendation, so its inclusion is disclosed rather than presented as an independent ranking. Synorb Streams scope what a routine should watch, and Manifests preserve the source URL, publication date, stable ID, and structured context. The feed can reach Town through MCP, REST, or webhooks, so a scheduled routine does not need to begin every run with a blank web search.
- Define one clear trigger.
- Give the routine only the tools it needs.
- Show the source and date for changing information.
- Require review for consequential writes.
For builders, Synorb's agent documentation provides a starting point for the source-grounded layer, while Town remains the place where the routine is configured and reviewed.