Drafts & approvals
A second pair of eyes.
Requires human approvaljamie@example.test
Re: Getting ready for launch
Thanks, Jamie. Here are the next steps for connecting your support inbox.
A conversation, not a one-off send
Can we pick up where we left off?Incoming message
The thread and its context are right here.Explicit reply
↗Received files / Thread context
More than a message.
Keep reference material alongside the conversation.
Downloads require scope and passing scan checks. Retention limits apply.
Integration credentials
Access, on your terms.
messages.readAllowedmessages.sendNot grantedinboxes.readAllowedSeparate credentials. Deliberate permissions.
Workspace / Production
Your agent inboxes
Getting ready for launch
support@mail.example.testNotes on the research brief
research@mail.example.testOctober invoice for review
finance@mail.example.testAgent inbox / Conversations
Research assistant
research@mail.example.test
A few notes on the research brief
Inbox configuration / Sender controls
Let the right mail in.
Separate rules for each inbox. Your application owns the next action.
partner@example.testAllowsender@example.testBlockAddress and domain rules—not decisions made by an AI.
Shipment update → customer inbox
The whole conversation.
Can you help me connect my inbox?
Agent inbox / Conversations
Customer support
support@mail.example.test
Getting our integration ready for launch
Drafts & approvals
A second pair of eyes.
Requires human approvaljamie@example.test
Re: Getting ready for launch
Thanks, Jamie. Here are the next steps for connecting your support inbox.
Developer tools / TypeScript
A few lines. A real inbox.
import { createDakNodeClient }
from "daknode";
const client = createDakNodeClient({
apiKey: process.env.DAKNODE_API_KEY
});
await client.http.POST("/v1/inboxes", {
body: { alias: "support-agent" }
});Your application owns the workflow
A conversation, not a one-off send
Can we pick up where we left off?Incoming message
The thread and its context are right here.Explicit reply
↗Here’s the revised project brief, with the original source notes attached.
Within the permitted inbox scopeNot a lost attachment.
October project review
Received files / Thread context
More than a message.
Keep reference material alongside the conversation.
Downloads require scope and passing scan checks. Retention limits apply.
message.received200support-agentpayloadmessage referencedestinationapp.example.testKeep the context.
“Could you send the supporting material with the revised brief?”
Webhooks / Delivery history
Follow every event.
200200503Signed events. Inspectable attempts.
Developer tools / TypeScript
A few lines. A real inbox.
import { createDakNodeClient }
from "daknode";
const client = createDakNodeClient({
apiKey: process.env.DAKNODE_API_KEY
});
await client.http.POST("/v1/inboxes", {
body: { alias: "support-agent" }
});Inbox configuration / Sender controls
Let the right mail in.
Separate rules for each inbox. Your application owns the next action.
partner@example.testAllowsender@example.testBlockAddress and domain rules—not decisions made by an AI.
Workspace / Production
Your agent inboxes
Getting ready for launch
support@mail.example.testNotes on the research brief
research@mail.example.testOctober invoice for review
finance@mail.example.testYour application owns the workflow
Initialize your DakNode infrastructure
Illustrative product views · synthetic data