Email and Slack
Ultron does not only live in the app. It has its own email address and it works inside Slack, so you can reach it where you already work. Email it a question, CC it on a thread so it can act, ask it to send an email for you, or @mention it in a Slack channel and watch it run a full turn in the thread. It is the same Ultron, the same account, the same memory — just a different front door.
Overview
- Email address
agent@ultron.uk- Slack
- Connect once, then @mention Ultron in a channel or thread
- Same everywhere
- One account, one memory — email and Slack are additional front doors
- Threading
- One Ultron conversation per email thread and per Slack thread
- Identity
- Every message is matched to your account and checked for authenticity
Ultron has a real inbox and its own address.
Ultron’s address is agent@ultron.uk. Write to it like you would write to a colleague. It reads the message — stripping quoted history and signatures so it focuses on what you actually said — and replies in the same thread. Each email thread is one Ultron conversation, so a back-and-forth stays coherent the way a chat session would, and its replies thread correctly in your mail client.
Three ways to use email
Direct, on CC, or as your sender.
| Way | What happens |
|---|---|
| Email Ultron directly (To: agent@ultron.uk) | Treated as a direct message. Ultron reads it, does the work, and replies in-thread. A bare “thanks” is just acknowledged, not acted on. |
| CC Ultron on a thread | Ultron stays quiet by default and records what matters — a task, a note, a CRM update. It only replies if the email actually asks it to, and it never adds recipients on its own. |
| Ask Ultron to send an email | Ask it to send something and it sends from its own address. Say “email me the summary” and it goes to your account email; ask it to send “as you” and it uses a mailbox you have connected. |
Slack
Ultron works inside your Slack, in the open, in the thread.
Connect Slack once from the integrations menu. After that, bring Ultron into any conversation by @mentioning it.
- 01@mention UltronIn a channel or a thread, mention Ultron with your request. It replies almost immediately with an “On it…” so you know it heard you.
- 02It reads the contextUltron picks up the surrounding thread, then runs a full turn — the same agent, skills, and memory as the app.
- 03Watch it workA live checklist streams in the thread, ticking off steps as they finish, so the work is visible rather than a black box.
- 04Get the answerIt posts the result in the thread, uploads any images there, and includes a link to open the full session in Ultron.
Ultron reaching out
The traffic goes both ways.
Ultron does not only respond — it can start the message. It can send you an email without you writing in first (for example, a scheduled briefing landing in your inbox), and it can post to Slack on its own: dropping a result into a channel, or letting you ask it, from chat, to message a Slack channel for you.
Identity and security
How Ultron knows a message is really from you.
Because email and Slack can drive real work on your account, Ultron has to be sure a message is genuinely yours before it acts.
| Channel | How you are established |
|---|---|
| The sending address is matched to your Ultron account, and the message must pass standard sender-authenticity checks. Both are required, so a forged sender address or a stranger emailing in cannot impersonate you or hijack a thread. | |
| Slack | Every Slack event is verified as genuinely from Slack, and the person who mentioned Ultron is resolved to their Ultron account before any work runs. An unconnected workspace is asked to connect first. |