Actions

Actions are reusable prompts and workflows.

Use them for tasks you repeat often: translation, grammar fixes, concise rewrites, summaries, follow-up replies, or context-aware workflows that should behave the same way every time. Fluent includes 34 default actions. The current default set is mostly text-focused, and later versions will expand further into Context, MCP, and Knowledge Base workflows.

You can run actions from the Smart Panel, from / search, from the Favorites bar, or from a dedicated shortcut.

Favorites

The Favorites bar can hold up to 8 actions. These are the actions shown directly in the Smart Panel.

Open the Actions window and drag action cards into the top row to add them. Drag to rearrange. Drag an action out of the row to remove it.

Use Favorites for the actions you run constantly. A smaller set usually works better than filling all 8 slots too early.

Create

Open Fluent from the menu bar, go to Actions, and click Create Action.

In the action editor you can configure:

• Name
• Prompt
• Variables
• Model override
• Auto Insert
• Grammar Mode
• Shortcut
• Icon and color
• Schedule

Start with a prompt that already proved useful in real work. Then make it reusable by replacing fixed values with variables and by keeping the instruction narrow.

Examples:

• Use {{ nativeLanguage }} instead of hardcoding one language
• Use {{ currentApp }} if the action should react to the current app
• Use {{ @My Writing Style }} or {{ @Product Docs }} if the action depends on Memory

Shortcuts

You can assign a dedicated shortcut to any action from the edit window.

Use shortcuts for actions you run frequently enough that opening Fluent and searching for them feels unnecessary. This works especially well for grammar fixes, translation, concise rewrites, and other high-frequency editing tasks.

Keep the set small. A few good shortcuts are useful. Too many quickly become hard to remember.

Auto Insert

Enable Auto Insert when the result should go back into the current app immediately.

This is best for predictable actions such as translation, grammar fixes, or simple rewrites. Fluent takes the selected text, processes it, and inserts the result back into the active text field without waiting in the Smart Panel first.

While the action is running, Fluent shows a small loading cursor around the current selection. This indicates that the selection was captured and is being processed.

If the action usually needs review, leave Auto Insert off and review the result in the Smart Panel instead.

Grammar Mode

Enable Grammar Mode for actions that should return an edited version of the input with highlighted corrections.

This is the right setting for grammar fixes, spelling corrections, and similar editing workflows where Fluent should highlight the changes.

For ad-hoc prompts, Fluent can also switch into grammar diff mode automatically when the request contains "fix grammar" or "fix spelling" phrases in prompt. Use Grammar Mode when the action should always behave that way.

Schedule

Actions can also run on a schedule.

In the action editor, choose a schedule if the action should run in the background. Fluent can notify you when it finishes. This is useful for recurring checks, summaries, or other small workflows that should happen without manual input each time.

The same view lets you set the action icon and color. That helps once the action appears in Favorites or in the Smart Panel often.

Examples

These examples are short on purpose. The prompt stays small, and the useful part comes from Context, Memory, or MCP.

Product Reviewer

Use this with browser context and a few attached comparison tabs.

Use the current browser page as the main product I am considering.
Use any attached tabs as comparison products.
Research the web for similar products, real reviews, repeated complaints, and strong positive signals.
Then give me a final verdict:
- Who this product is good for
- Who should avoid it
- Whether this is the one to buy or a better alternative exists
Keep it practical and decisive.

Inbox To Reminders

Use this with selected email text, meeting notes, or a messy task list.

Review the selected text and extract only real action items.
Create them in Reminders if that integration is available.
Use short and clear task titles.
Only add due dates when they are explicitly mentioned.
If something is vague, leave it without a date instead of guessing.
Then show me what was created and what was skipped.

Reply From My Docs

Use this when the answer should follow your own documentation and tone.

Draft a reply based on the current context.
Use {{ @Product Docs }} and {{ @My Support Style }}.
If helpful, also search my Knowledge Base for relevant details.
Be clear, warm, and direct.
Do not invent facts, policies, or product behavior.
If something still needs confirmation, say that plainly at the end.

Project Pulse

Use this when the current page or document should be combined with project tools.

Use the current context as the starting point.
If project MCP tools are available, gather the latest related issues, pull requests, or notes.
Then write a short project update in the style of {{ @Team Update Style }}.
Include:
- What changed
- What is blocked
- What needs attention next
Keep it short enough to send to a team chat.