The hardest part of a first agent is the blank box. Templates exist so you don’t have to start there.
Xagent ships with templates for common jobs: a support chatbot, inbound lead handling, LinkedIn posts, email, long-form content, inbox management, slides and documents. Each one starts with a role and a set of tools already in place. You change what doesn’t fit.
Pick the closest template
Choose the template nearest to the job, not the perfect one. If your support team answers the same twenty questions all week, start with the support chatbot. If marketing spends Monday writing the week’s posts, start with LinkedIn post.
Give it your own material
A template knows the shape of the job. It doesn’t know your products. Upload your docs to the knowledge base: help articles, price lists, policy PDFs, past reports. Xagent searches them with hybrid search, which mixes keyword and meaning-based matching, so an agent can find “refund window” even when the document says “returns period”.
Connect the tools it needs
Most templates need at least one connected account, for example Gmail for an inbox agent, or LinkedIn for a posting agent. You authorise the account once in Xagent, and the agent uses it from then on. Anything without a native connector can come in through MCP, which has its own post.
Choose the models
Xagent works with open models and API providers, including any OpenAI-compatible endpoint, so you’re not tied to one vendor. If you’re not sure which to use, leave the defaults and change them once you’ve seen a few runs.
Save it, then decide when it runs
Run the agent a few times by hand first. When the output is what you’d have written yourself, save it and add a trigger. Triggers can be a schedule, like every Friday at 9am, an incoming webhook, or a new email in Gmail.
The first agent most teams keep is a dull one, like a weekly report or an inbox sort. That’s fine. Dull is where the hours are.
