Give Your AI Agent an Email Address in Clanker Workspace

An email can be the request that starts the work. “Prepare a launch checklist from the brief” is a task for an Agent with access to that brief, rather than just a message to summarize.

Clanker Workspace supports managed addresses at email.clankercloud.ai. Link an address to a Project and a hosted Agent, choose the senders allowed to request work, and the Agent uses its configured project context and capabilities to handle those requests. A new email thread creates a Workspace Session; replies continue it, and the response is emailed when the work finishes.

Choose a job for the address

For a first example, use a fictional internal launch assistant. Its job is to read the current brief, save a readiness checklist, and return a short summary of missing inputs. It does not approve a launch or promise delivery dates.

Create and test the Agent in a normal Session first. Add the brief and checklist to the Project, then check whether the Agent identifies missing information correctly. The custom Agent guide covers this setup.

Managed email uses hosted Workspace Agents. A Claude MCP connection or a native BYOA registration does not itself make that assistant the worker behind a Clanker email address. For those routes, see the agent workspace overview.

Create the address and save its routing

Managed email is available on Business, Business Pro, and eligible Enterprise accounts, including Unlimited entitlements. Eligible accounts can have up to five Clanker addresses. Check the account's current eligibility and plan details before setting up the channel.

Open Settings → Email accounts or the Project's Email tab:

1. Create the managed address using the available address controls.
2. Choose the Project whose files and instructions the work should use. General is also supported.
3. Select the hosted Agent for the role. No agent uses your regular Session defaults.
4. Save the email addresses allowed to send requests.
5. Review the Agent's instructions and permitted Tools before completing setup.

After saving, permitted requests start automatically. There is no confirmation for each incoming email. For the first trial, allow only a test sender you control and use fictional inputs.

These managed addresses are separate from a personal mailbox connected through Channels. Use managed email when you want a dedicated address for Agent work. Use the supported mailbox connection when your workflow needs an existing inbox and its configured channel controls.

Send a request you can check

From the allowed test sender, send an instruction such as:

Using the launch brief in this Project, prepare a readiness checklist for the internal review. Save the checklist in the Project. In your email response, summarize missing approvals, missing inputs, and any deadline that needs confirmation. Do not contact clients or approve the launch.

Inspect the resulting email Session in Workspace. Read the saved checklist and compare the reply with it. An email response and a generated file are different deliverables; do not assume files are automatically attached to the message. Verify the output and the recipient's access before depending on a delivery method.

This example is a proposed trial, not a customer result or a measured delivery guarantee. Before using the address for a live process, check an ordinary request, an incomplete brief, and a request outside the Agent's role.

Understand the thread's behavior

Replies within the email thread continue its existing Session. This keeps the conversation attached to the work already started. Treat the correspondent's message as input to the configured job; it should not authorize unrelated client access or override the owner's instructions.

Opening the Session in Workspace keeps email replies enabled. Sending your first message in Workspace permanently converts that thread to a regular Session and stops its email replies. If you want the conversation to remain an email thread, review it without posting a Workspace message.

Moving the address to another Project or relinking its Agent changes new conversations. Existing threads retain their original context. Renaming changes the actual address and stops requests to the old one; deleting stops incoming requests and outgoing replies while preserving Workspace conversations.

Keep the workflow useful as it grows

Use dedicated roles and clear project context. A proposal-review address should have the purchasing checklist; a reporting address should have the current reporting inputs. An email address supplies the trigger, not missing business knowledge or access to every application.

Review Sessions, outputs, and usage as requests arrive. Agent work and its selected paid operations use credits. If the task needs to run every week even without an email, configure a separate Schedule for the hosted Agent.

Sources

• Workspace email account setup and thread behavior
• AI employee: requests through managed email
• Build a custom Agent
• Existing mailbox workflows
• Current pricing and eligibility