Skip to content
ClickRuntime

Automate Front

Keep your Front inboxes moving. Conversations that sit too long without a reply get flagged, each inbox's open and unassigned load is reported, and conversations that have gone quiet are archived. Describe what you want to your AI assistant, check what it will do, and it keeps running with your laptop closed.

Add to ChatGPTAdd to Claude
Works inChatGPTClaudeClaude CodeCursorCodexVS CodeGemini CLIZedopencodeAny MCP client

Try asking

Create a ClickRuntime automation: every 30 minutes, post to #support in Slack any open Front conversation in the Support inbox that has had no reply for 2 hours.

Paste it into your assistant. It tells you what it will send or change before it runs live.

Ideas

What you can automate in Front

Alerts for customers left waiting, a morning count of what's open in each inbox, and old conversations cleared out on their own. These are ready-made starting points. Anything else you can describe works too.
On a schedule

Get alerted to Front conversations with no reply

Customers waiting more than two hours are flagged to you once, before they write again.

See how it works
On a schedule

Get a morning count of open Front conversations

Each morning you see how many conversations are open and unassigned in every inbox.

See how it works
Daily

Archive Front conversations that have gone quiet

Conversations with no activity for two weeks are archived each night, and you get the count.

See how it works Your own logic

Any other automation you can describe in words

Your own rules, schedule and AI steps with Front, plus any other app. Describe it and your assistant builds it.

See how to build your own

Build your own

Build any Front automation you can describe

The ideas above are ready-made starting points, not a fixed list. Describe what Front should do in your own words, with your conditions, other apps or an AI step, and your assistant writes it, tests it and runs it on ClickRuntime.

  • Your own rules

    Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.

  • Any number of apps

    One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.

  • AI where it helps

    Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.

  • On a schedule or on each event

    Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.

For example, ask your assistant

Every 30 minutes, find Front conversations waiting over four hours for a reply and tag them as urgent.

When a Front conversation is tagged bug, create a Jira issue with the customer message and a link back.

When a new Front conversation arrives, have AI classify it, assign it to the right teammate, look up the customer in HubSpot and add a comment with their plan.

Beyond chat

Have Front work when you're not in the chat

Connecting Front to ChatGPT or Claude lets you ask about it while you chat. ClickRuntime handles the part that should happen on its own: checks on a schedule and actions on each new event, set up from the same chat and running after you close it.

Setup

Connect Front

You connect Front with an API token a Front admin creates. The admin picks scopes covering shared and private resources.

Front

Shared inbox

  1. In Front, go to Settings → Developers → API tokens. Only admins can do this.
  2. Choose Create API token and select the scopes, such as shared resources for team inboxes.
  3. Copy the token.
  4. In the ClickRuntime dashboard, open Connections & secrets and save the token as a secret for Front.

Good to know

Front limits that affect automations

  • Only Front admins can create API tokens.
  • The token reaches only the resources its scopes cover. Shared inboxes and private inboxes are separate scopes.
  • Front limits API requests by plan, so large inboxes are read in pages and automations that check them run every few minutes rather than constantly.
  • Archiving needs a token that can write, not just read.

FAQ

Questions about automating Front

What can ClickRuntime see in Front?
The inboxes and conversations your token's scopes cover. With read access it can list conversations, their status and last messages. With write access it can also change a conversation's status, for example to archive it.
How quickly does it notice a conversation waiting too long?
The unreplied alert checks on a schedule you choose, such as every 30 minutes, and tells you about each conversation once.
Will archiving delete anything?
No. Archiving changes the conversation's status in Front rather than deleting it. The nightly job emails you how many it archived.
Can I choose which inboxes it watches?
Yes. Name the inboxes when you describe the automation, like Support or Billing, and it only looks at those.
Do I need AI for Front automations?
No. Alerts, counts and archiving run without it. Summaries or reply drafts use the AI that comes with every ClickRuntime plan, so no AI key of your own is needed.
Is this a Front connector for ChatGPT or Claude?
Not for chatting with Front data. A chat connector lets your assistant read and change Front while you're in the conversation. ClickRuntime is for the work that should happen without you: you set up an automation from the chat once, and it keeps running on a schedule or on each Front event.

Related pages

Keep exploring

Tell your assistant what Front should do

Free plan. No credit card.

Add to ChatGPTAdd to Claude