Grok Bot for Front: Work a Shared Inbox Without the Risk
Want a Grok Bot working your Front inboxes? Connect Front to Carly with your API token, add the Carly connector to Grok Bot once, and every Bot works your Front inboxes through one connection where every action names the inbox and customer-facing replies can wait for approval.
Cursor’s plugin marketplace, which is where Grok Bot gets its connectors, has no Front plugin. So the default route is a Bot clicking through Front’s web app in a browser that every one of your Bots shares.
The quick answer: put Front in Carly, then point Grok Bot at Carly. One token, scoped by you, and no Front login sitting in a shared browser.
1. Connect Front to Carly
Front hands out API tokens on every plan, and only an admin can create one. The token belongs to the company rather than to a person, so name it something you will recognize in six months, like “Carly for Grok Bot, support team”.
- In Front, open Settings, then Developers, then the API Tokens tab.
- Click Create API token and give it that descriptive name.
- Under features, choose Access resources.
- Under namespaces, pick the shared workspaces the Bot should reach (or all of them).
- Set permissions per resource: Read and Write for conversations, tags and contacts, plus Send only if Bots will reply to customers. Click Create, then Copy the token.
- Paste your API key into Carly on the integrations page.
Carly connects to thousands of apps, so while you are on that page, connect the Gmail or Outlook mailboxes behind your Front channels, HubSpot for customer records, and Slack for escalations. The Front integration page lists what Carly can do inside Front.
Front also runs an official MCP server, in open beta, that needs an admin-built OAuth app with a client ID and secret. If you prefer it, Carly can add it under Integrations → MCP servers.
2. Add Carly to Grok Bot
- Select Plugins in the Grok Bot sidebar, or tap your avatar and choose Plugins on mobile.
- Add Carly’s remote MCP server,
https://carlyassistant.com/mcp/. - Finish the authorization in the browser tab that opens. If it sits on Waiting for authorization, use Reopen.
- Sign in to the Carly account holding your Front connection.
- Confirm Carly appears under Installed.
The Front token lives in Carly. No Bot ever types a Front password into the shared browser.
What one Bot can do afterwards
- Triage the shared inbox. Read new conversations in support@, billing@ and sales@, and sort them by topic and urgency.
- Assign and tag by rule. “Refund requests go to Emily, bug reports go to Josh, anything from Shopify merchants gets the
merchanttag.” - Reply from a real support address. Draft and send answers from the channel the customer wrote to, threaded in the Front conversation, so your teammates see the reply where they work.
- Chase SLAs. Flag any conversation waiting more than four hours and nudge its assignee with an internal comment.
- Send a daily digest per inbox. Open conversations, oldest waiting customer, and what closed yesterday, emailed to Claire at 8am.
- Escalate by rule. Anything mentioning a chargeback, a cancellation, or a named account like Stripe goes to Slack with a summary instead of an auto-reply.
Put a Require approval rule on customer-facing sends while you build trust. Carly holds the reply, with the inbox and recipient named, until you approve it. You can run the same triage as a standing workflow described in plain English that fires without a Bot open, or hand it to a named Carly agent with its own email address that Michael can CC on hard threads.
The shared browser route, and what it costs you
Grok Bot’s docs are direct about it: prefer a connector when one exists, and use the browser for services without one. Front has none, so a Bot signs in to Front’s web app on Grok Bot’s cloud computer and works the queue by clicking.
One seat, one login, every Bot. Every Bot on your account shares that computer. SpaceXAI’s docs say browser sessions are shared, that signing in for one Bot makes the session available to your other Bots, and that the separate screens “are separate work surfaces, not separate security boundaries.” The Bot you set up to tag conversations can also send from your biggest customer’s thread.
It acts as whoever signed in. The browser holds one teammate’s Front seat, so every action lands under that person’s name with that person’s permissions. If it is an admin seat, every Bot is an admin.
Sessions drop mid-task. SpaceXAI notes that some websites expire sessions, enforce short timeouts, or ask for verification again, and tells you to have the Bot pause and notify you. A routine that ran overnight stops at a login screen.
No dry run. Grok Bot has Auto-review rules (“ask first before sending any external email”), but SpaceXAI calls Auto Review model-based and says it should complement least privilege rather than replace it, and an approval does not reverse work already done. Nothing previews what a routine will click before it runs.
Clicking is fragile. A Front interface change, a new modal, or a slow load, and the Bot misfiles a conversation instead of failing cleanly.
Grok Bot’s shared browser next to Carly
| Need | Grok Bot’s shared browser | Carly connector |
|---|---|---|
| Setup | Sign a Bot in to a Front seat | Paste one scoped API token |
| Limit what Bots can do | Whatever the signed-in seat can do | Read, write and send chosen per resource |
| Keep Bots apart | No, one login serves every Bot | Every action names the inbox |
| Survive a session timeout | Stops at the login screen | Token does not expire with a browser session |
| Approval before a customer send | Model-based Auto Review on a click | Require approval rules on the send itself |
| Gmail, Outlook, HubSpot alongside | Separate plugins, separate logins | Same connection list |
| Runs on a schedule | Routines on the shared machine | Workflows and agents, with or without a Bot |
Carly offers free Zapier-style workflows; AI agents from $35/month.
Quick fixes
| Problem | Fix |
|---|---|
| Bot hit the Front login screen overnight | Connect Front in Carly so no browser session is involved |
| Carly cannot see an inbox | Edit the token’s namespaces to include that shared workspace |
| Replies fail but reads work | Add the Send permission to the token |
| Private inboxes missing | The teammate must turn on API access in their own Front settings |
| Replies going out before review | Add a Require approval rule for external sends |
| Chargebacks need a human | Add an escalation rule that posts to Slack and holds the reply |
Frequently asked questions
Does Grok Bot have a Front integration?
Not in Cursor’s plugin marketplace, which is where Grok Bot’s connectors come from. Without one, a Bot works Front through the shared browser. Connecting Front to Carly with an API token and adding the Carly connector gives every Bot a structured route instead.
Do I need a particular Front plan for an API token?
No. Front offers API tokens on every plan, with higher rate limits on higher tiers. You do need to be a Front admin to create one.
Is it safe to sign a Grok Bot in to Front?
Every Bot on your account shares one cloud computer and its browser sessions, so one Bot’s Front login is every Bot’s Front login. Keeping the connection in Carly means you choose the token’s permissions, and approval rules sit in front of customer sends.
Can one Bot cover Front, Gmail and HubSpot together?
Yes. Connect all of them to Carly and one Bot works across all of them, with each account kept separate. Get started.
What if our Front setup has unusual inboxes or rules?
Multi-brand workspaces, private inboxes, and custom routing all work through the token’s namespaces and permissions. For a walkthrough on your own setup, book a call with the Carly team.
Related: Grok Bot · Grok Bot for HubSpot Service Hub · Multiple Gmail accounts in Grok Bot · Front AI · Claude and Front · Best AI assistants for Front
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
