The maxinja assistant

Open maxinja beside your campaign or workflow, attach the item you want to work on and send your brief. The conversation stays with you as you move between pages, so you can investigate an audience, refine its email and review the resulting campaign in the same chat.

New to maxinja? Start with a campaign brief you can follow. This reference covers the chat controls; the overview explains its capabilities and costs. maxinja runs inside the app; the Public API does not start these conversations.

Opening the pane

The pane has three sizes:

On a narrow window, maxinja opens in full view instead of a side panel.

Chats

Each conversation is a separate chat. From the pane header you can:

• Start a new chat.
• Open the chat list to search conversations, grouped into Starred and Not Starred.
• Rename, star, or delete the current chat once it has messages.

Titles are generated automatically from your first message.

Chats belong to the user who started them, within that space. Your history list does not show another member's conversations. Saved broadcasts, templates and workflows have their own workspace access: a private chat can change work your teammates can open.

Search matches chat titles. Rename a useful conversation with the campaign or task name, and star it for later reference. Start a new chat when the customer goal changes substantially or you need a clean attachment history. A chat does not isolate product changes: two chats targeting the same broadcast still work on the same saved broadcast.

Writing a request

Type in plain language. Enter sends; Shift+Enter adds a line. Name the item, the change and the state you want to leave it in:

Shorten this campaign’s introduction to two sentences. Keep the offer, price and button link unchanged. Leave it unscheduled.

Attach the current campaign before sending. For a new campaign, include the audience and the intended customer action. See how to write a brief.

Adding context

maxinja is one assistant for the whole space. You point it at a specific thing by attaching a reference to your message.

• @ or # (or the Add context button) opens a picker for schemas, segments, templates, broadcasts, workflows, webhooks, forms and brand kits. To attach an individual contact or object, open its record page and choose Current view; the picker does not search all individual records.
• The Current view chip attaches the page you are on. With it attached, "add a condition for recent buyers" needs no name.

Workflow-step and email-part controls can attach the selected step or passage. Check the chips on the message before sending so the request targets the right item.

References attach per message, so one chat can move between entities.

Opening a page alone does not attach it. Inspect Current view and the reference chips before sending. For a follow-up, attach the saved campaign and name the part to change, such as its introduction or audience. That avoids creating another item when your intention is to revise the existing one.

The attachment identifies the item, rather than taking a permanent copy of all its settings. maxinja can load its current saved state and investigate other workspace data when needed. A request such as “use the attached Order record” supplies a starting point; it does not restrict every query to that one record.

What context is used

The conversation includes previous retained messages, your attachments and referenced items. maxinja also has product reference tools, workspace data tools and the specialists that work on campaigns, templates and workflows. A data investigation reads workspace facts; a specialist can edit its saved product item. Selected MCP servers add external tools.

Supply product facts that are absent from your records: the approved price, dates, destination link and required wording. Treat customer notes, files and tool results as evidence to inspect. A confident answer is not evidence that an order exists or that a campaign was delivered.

Attaching files

Attach with the paperclip, drag-and-drop, or paste. Accepted types: .png, .jpg, .jpeg, .pdf, .txt, up to 100 MB each. Each attachment shows upload progress and can be removed before you send.

Wait until uploads finish before sending. Files remain in the conversation's history after that message, so a model selected for a later request must also support the earlier images or documents. Use a new chat for a text-only task if those files are irrelevant to it.

During a run

maxinja handles one request at a time. While it works, it:

• Shows progress updates and its reply as it works.
• Hands larger jobs to helper agents and reports back what each one did. See the agentic flow.
• Shows a preview of what it built, with a button to open it.

Messages sent during a run steer that active work. Include the correction and the result it applies to. You can also stop the exchange; completed changes remain saved. If maxinja asks you a question mid-run, you answer it in the question's own input.

Queued guidance appears above the composer until the active work consumes it. Several corrections can be combined into the pending guidance; they do not create independent jobs that all start at once. A correction takes effect at a checkpoint, so inspect already-saved changes when the direction changes.

When maxinja asks a question

maxinja can ask for a decision inline, often with suggested answers to click. While it waits, the main composer locks so your reply goes to the question. Some questions show a countdown and apply a default if you do not answer in time.

Stopping and editing

Editing or removing conversation history does not restore an earlier campaign state, refund incurred AI usage or reverse an external tool action. Before retrying a failed publication or send request, open the product item and check whether that action completed. Continue from the actual saved state with a specific repair request.

The assistant records an exchange as processing, completed, aborting, aborted or failed. Stop requests interruption; an aborting exchange is still settling that request. A completed exchange means the assistant finished its response, while a failed exchange includes a reason to inspect. Neither status alone proves delivery or a complete workflow run.

Choose tools and models for the conversation

The session’s AI settings choose its model and registered MCP servers. A running exchange retains the selection it started with. Change settings for subsequent work, or stop and start a new request when the task requires a different capability.

An image or PDF already in the conversation remains part of its context. A model that cannot accept that modality is rejected rather than silently substituted. For connected MCP tools, review the selected server and the task you are authorizing: those tools can perform actions in the connected service, and deleting this chat will not reverse them.

Workspace conversations require write access. A read-only role cannot start a workspace run merely because the question itself sounds read-only.

Workspace defaults

An admin opens Settings → maxinja → General to set Model and Editor autocomplete. The workspace model seeds new chats and generation actions. Existing conversations retain their own selection; use AI settings for this session in the composer to change one chat.

Automatic autocomplete suggests a continuation while you write Liquid in the email editor. Accept the faded suggestion with Tab. Each generated suggestion uses AI credits. Off disables these suggestions for the whole space. The choice does not stop chat or change published workflow execution.

The MCP servers tab manages the space's registered servers. In an individual chat's MCP menu, select the servers that task needs. Registering a server and granting it to a conversation are separate choices. AI workflow steps have their own tool grants, model and thinking settings, as do email templates that use Adaptyle.

Model compatibility and connected tools

Choose from the models currently offered in the picker. An unsupported attachment or capability causes a selection error before inference. Choose a compatible model explicitly and retry only the work that remains. Increasing model capability or thinking depth does not supply missing business facts.

MCP tools run in the connected service and can have external effects. Review the registered endpoint, credentials and available tools with your administrator. Grant a server only when its tools fit the task. Stop, chat deletion and removal of a tool selection do not reverse an action the connected service already accepted.

Suggestions and usage

The empty chat shows starter suggestions. Selecting a suggestion fills the composer; inspect and edit it before sending. Opening the pane or checking saved suggestions does not start a paid suggestion generation.

Generate personalized suggestions (uses credits) explicitly requests a generation using workspace context. While it is generating, Check saved suggestions reads its result without starting another call. An unknown generation outcome needs reconciliation, and unresolved credits stay reserved; repeatedly opening the pane does not regenerate it.

Assistant work is paid from the shared workspace wallet. New briefs, revisions, delegated work, generated images and recipient previews can add usage. There is no fixed total price for a conversation and no monthly AI allowance. See AI and usage credits.

Privacy and retained history

Chat ownership controls who can open the conversation; it does not prevent the selected model or connected tools from receiving the context needed for your request. Include the files and customer facts required for the job and review external tool grants before sending.

Deleting a chat or deleting messages removes that visible conversation history. It does not delete the customers it referenced or undo saved campaign work. Source-record deletion can also remove assistant-generated history that read that private data. Your submitted text can remain while generated answers and tool results are removed. Removed private exchanges are not reused as model history or replayed.

If older evidence is no longer available, investigate the current source again with data you still have permission to read. Avoid treating an old answer as a current customer profile. Access is checked when work is requested and while it executes; losing workspace write access can stop an exchange.

Recover from an incomplete request

For a campaign, check the audience, sender, email and schedule. For a workflow, inspect the draft, publication state and run history. While maxinja works explains how saved changes differ from execution outcomes.

Previews

When maxinja produces something to review, it opens a preview in the right of the workspace:

• Audience preview: which schema it filters, the filter in plain English, what it references, and how many contacts match out of the total.
• Email preview: a rendered sample to inspect. A later personalized render can use newer data and produce different wording.

Attachments and generated files open there too. Switching maxinja to full view clears the preview.

Related

• maxinja overview
• The agentic flow
• Broadcasts
• Templates
• Adaptyle