Integrations · Front
Guild agents read and manage Front conversations, contacts, inboxes, and knowledge bases on your team’s behalf. Credentials are stored and injected server-side, so agent code never sees the API token. Credential policies let you restrict which operations each agent can call, and every request runs through Guild’s audit trail.
Book a demo
See how teams govern agents that use Front.
Talk to sales
Get access to Guild, then connect Front to your first agent.
What the Front integration exposes
The integration is published asguildai~front-openapi and surfaces tools that cover conversations, messages, drafts, contacts, inboxes, tags, message templates, signatures, knowledge bases, analytics, shifts, time off, and teammate and team management. Tools follow the front_openapi_ naming prefix. Use pick() from the SDK to include only the tools your agent needs.
How it works
1
Open credentials in Guild
Go to Access & setup > Credentials in Guild and click Connect. Search for and select front-openapi.
2
Paste your Front API key
Paste your Front API token into the API Key field. Guild sends the key as a bearer token in the
Authorization header on every request.3
Scope the credential
Choose whether the credential serves the whole account, one workspace, yourself only, or a single agent. See Credentials for details on each scope.
Why Front access needs governing
Front tools can send messages, delete conversations, manage teammates, and modify inboxes. Guild stores the API token server-side and injects it through its credential proxy, so agent code never handles the secret directly. You can scope each credential to an account, workspace, member, or single agent using Credentials, limiting which workspaces and agents can reach Front at all. Credential policies let you writeALLOW and DENY rules against specific front_openapi_ operation names. A policy can permit read operations like front_openapi_list_conversations while blocking destructive ones like front_openapi_delete_conversation, and rules can be scoped to individual agents or workspaces on the same credential. Every request is checked inside the proxy before it leaves Guild; agents cannot bypass the check.
About the Front integration
Agents can read and manage Front inboxes, contacts, conversations, and tags. They can send messages, create drafts, manage message templates and signatures, and work with knowledge bases and articles. Team and teammate management tools are also available, including shifts, time off, and contact groups. The integration isguildai~front-openapi.
Authentication
- Type: API key
- Header: Guild sends the key as a bearer token in the
Authorizationheader
Setup
1
Connect Front
In Guild, go to Access & setup > Credentials, click Connect, select front-openapi, and paste the key into API Key.
Usage
Selecting specific tools
Tools are named with thefront_openapi_ prefix. Use pick() to include only what your agent needs.
Tools
Tools in the latest published version ofguildai~front-openapi:
All 225 tools
All 225 tools
Frequently asked questions
Can my agent send a message from a Front channel?
Can my agent send a message from a Front channel?
Yes. The
front_openapi_create_message tool sends a new message from a channel, and front_openapi_create_draft creates a draft as the first message of a new conversation.Does the integration support webhook events from Front?
Does the integration support webhook events from Front?
No. The catalog entry for
guildai~front-openapi lists no webhook events, so the integration does not receive inbound event triggers from Front.How do I stop one agent from deleting conversations while letting another read them?
How do I stop one agent from deleting conversations while letting another read them?
Write a
DENY rule targeting front_openapi_delete_conversation scoped to the agent that should not delete, and an ALLOW rule for read operations. Guild’s credential proxy enforces the rules before any request reaches Front. See Credential policies for rule syntax.Can I use the integration to manage knowledge base articles in multiple languages?
Can I use the integration to manage knowledge base articles in multiple languages?
Yes. The tools include
front_openapi_create_article_in_a_knowledge_base_in_specified_locale and front_openapi_get_knowledge_base_article_with_content_in_specified_locale, which create and fetch articles for a given locale alongside the default-locale equivalents.Put a governed agent on Front this week
Book a demo
See how teams govern agents that use Front.
Talk to sales
Get access to Guild, then connect Front to your first agent.