Workweaver User Guide
Workweaver helps you run real work with AI and still keep control. The launch surface is built around one loop: describe the job, connect the missing tools, approve the plan, get proof.
Start Here
- Open /auth/ and sign in with Google, Microsoft, or Zoho.
- Start with one flagship workflow: Morning Briefing, Inbox + Calendar Triage, or Lead Follow-up Agent.
- Open Connection Center and connect only the tools that workflow still needs.
- Review the plan, approve any gated actions, and let the run execute.
- Inspect proof cards, approvals, and the evidence trail afterward.
What You Can Do Today
- Run flagship workflows that combine research, outreach, triage, follow-up, and operator review.
- Connect Gmail, Google Calendar, Slack, HubSpot, Salesforce, WhatsApp, and a standards-based custom path for long-tail integrations.
- Use Workweaver voice, meeting follow-through, calendar automation, AI teams, and AI coding workers from the same product.
- Review outcomes through Proof Cards, Decision Trace, and the Evidence Trail instead of trusting a black box.
What “Proof” Means
- High-risk actions stay approval-gated.
- Workweaver records the plan, approvals, outputs, and linked evidence for each run.
- If a provider degrades or a capability is unavailable, the product surfaces that honestly instead of pretending the run succeeded.
Connection Guidance
- Start with the minimum connector set needed for the workflow you chose.
- Gmail, Google Calendar, and Slack are the default first-run connectors.
- CRM support is strongest today through HubSpot and Salesforce.
- Standards-based OAuth2, REST/OpenAPI, and webhook paths remain available for deeper or custom integrations.
Voice, Meetings, and Coding
- Voice and meeting paths are real product surfaces, but they still follow the same rule: honest degradation, explicit consent where required, and proof after the run.
- AI coding workers can clone or fork repos, run plan/edit/test loops, and stop at approval before push or PR delivery.
Troubleshooting
Sign-in or OAuth callback failed
- Confirm the provider returned to Workweaver, not a stale login route.
- Retry through /auth/.
- If the problem persists, use the public contact path at /about/.
A run shows partial or a warning
- That usually means an external provider was unavailable or skipped.
- Workweaver surfaces per-channel results so you can see what actually happened.
A workflow needs more tools than are connected
- Go back to Connection Center and add only the missing systems.
- The goal is to finish one workflow with proof, not to pre-configure everything.
Known Boundaries
- Workweaver operates through cloud, SaaS, and channel execution. It does not control your desktop or local apps.
- Mobile parity is still behind the desktop experience.
- Some WorkMemory extraction paths remain partial when vision infrastructure is not configured.
- Some older memory routes are still mounted while the canonical contract rollout finishes.
Public References
Common Questions
Where should I start? Use /auth/, then pick one flagship workflow instead of configuring everything at once.
What happens if an AI provider is unavailable? Workweaver degrades honestly and surfaces partial or skipped steps instead of pretending the run succeeded.
Can Workweaver handle coding tasks? Yes. AI coding workers run plan/edit/test loops and stop at approval before push or PR delivery.