Clanker CloudAn email task can begin inside Workspace as well as arrive from outside it. You might need to ask a client for the missing images, confirm a requirement, or follow up on a decision already recorded in a Project.
Where Clanker email sending is available for your account, the Session composer lets you choose an active managed Clanker address linked to a hosted Agent. Your request can specify the recipient, initial message, and how the linked Agent should handle subsequent replies.
Prepare the mailbox and its Agent
First create and configure the managed email account on an eligible plan. Link an Agent that can run in Workspace and check its Project, instructions, and Tools. The managed email guide covers eligibility, allowed senders, and routing.
Only active addresses linked to an Agent appear as selectable email accounts in the composer. Choosing Clanker email identifies the sending account. The selection alone is not a request to send a message.
This route uses the linked hosted Agent for replies. It is separate from connecting Claude, OpenClaw, or Hermes through MCP or BYOA.
Draft an explicit request
For a first trial, use a test inbox you control. Supply its exact address yourself, along with a subject and the facts the message may include. Prepare a draft before asking for delivery:
Draft an email to the test recipient I named. Subject: Launch images needed for review. Ask for the three product images listed in the current brief. Explain that the launch date is still awaiting approval. Show the message for review and do not send it yet.
Check the draft against the brief. Does it ask for the right assets? Does it preserve the unconfirmed launch date? Does it reveal only the information appropriate for this recipient?
When ready, give an explicit sending instruction naming the recipient and selected mailbox. Choose the approval mode appropriate to the task and check any action request that appears. AUTO approves enabled actions, so do not assume every sending setup pauses for a separate approval.
Specify how replies should be handled
The initial request can include follow-up instructions for the linked Agent. For this fictional launch task:
Handle replies only about the requested product images.
Record which images the sender says are ready and what is missing.
Use the current Project brief to answer factual questions.
Do not agree to a new launch date or additional deliverables.
If the sender asks for a decision outside this role, flag it in
the Workspace Session for the owner.
These owner instructions define the conversation's job. A correspondent's reply supplies task input; it does not grant authority to change that job or expose unrelated Project material.
The selected mailbox determines the sending identity and linked reply Agent. The follow-up conversation uses that Agent's assigned Project, or General when it has no assigned Project. Check that context before relying on the Agent to answer from the correct brief.
Verify the conversation before repeating an action
The outbound message starts a dedicated email conversation Session. Inspect its history and test-inbox delivery, then send a reply from the test recipient and examine the Agent's response and saved work.
If delivery is uncertain, inspect the conversation and destination before asking for another send. A timeout is not proof that nothing was sent. This walkthrough is a suggested acceptance test, not a claim that your mailbox has already passed it.
Opening the email Session preserves email replies. Sending your first Workspace message in that thread permanently switches it to a regular Session and stops its email replies. Keep that behavior in mind when the owner needs to take over.
For incoming client requests, use the intake brief workflow. For recurring internal work, configure a Schedule separately instead of assuming that selecting a mailbox creates recurrence.
Sources
Give your assistant one useful job
Use a linked Clanker mailbox for an explicit email task and keep the resulting reply conversation in Workspace.