Integration

Re:amaze
automation.

16 automated actions available through Cerebral OS. Connect Re:amaze to any workflow, Cerebral, or Map — with full governance, audit trail, and dry-run safety on every execution.

16 actions · tickets · governed execution

Execution trace
live
16
actions
100%
governed
<200ms
latency
16
Automated actions
6
Read operations
10
Write operations
2,800+
Compatible Maps
Actions

What you can do
with Re:amaze.

Every action below is available as a verb in Cerebral OS — callable from a Cerebral, a Map, or the Runtime API. All executions are governed, audited, and dry-run safe.

Add Note
reamaze:add_note
Add an internal staff note to a conversation (customers cannot see these notes). This is a convenience wrapper for creating a message with visibility=1 (internal). Use this for staff communication, NOT for customer-facing replies.
Write Low risk
Apply Macro
reamaze:apply_macro
Apply a canned response/macro/template to a conversation with variable substitution. Re:amaze calls these "Response Templates" - this is the standard macro/canned response system. IMPORTANT: Provide EITHER template_id OR template_name (not both). template_id is more efficient. Variables like {{customer_name}} and {{order_id}} are automatically replaced with values from props.variables. Returns the customized message body that was sent to the conversation.
Write Medium risk
Assign Conversation
reamaze:assign_conversation
Assign a conversation to a specific staff member. This is a convenience wrapper for updating conversation with assignee field. CRITICAL: Use this to escalate tickets to humans when AI cannot complete the task.
Write Low risk
Create Contact Note
reamaze:create_contact_note
Add a staff note to a customer's contact profile (not to a specific conversation). These notes are visible to all staff members when viewing the customer's profile. Use this for permanent customer information that should persist across all conversations.
Write Low risk
Create Conversation
reamaze:create_conversation
Create a new Re:amaze conversation/ticket on behalf of a customer. This is useful for creating tickets from custom forms, API integrations, or automated systems. The conversation will appear as if the customer initiated it.
Write Medium risk
Create Message
reamaze:create_message
Create a new message (reply) in an existing Re:amaze conversation. CRITICAL: This is the primary way for AI to respond to customer tickets. Use visibility='public' for customer-facing replies, visibility='internal' for staff notes.
Write Medium risk
Get Articles
reamaze:get_articles
Retrieve knowledge base articles from Re:amaze. Use this to search help documentation, FAQs, and support articles. Useful for AI to reference when answering customer questions.
Read Low risk
Get Conversation
reamaze:get_conversation
Execute get_conversation action via reamaze
Read Low risk
Get Conversations
reamaze:get_conversations
Get conversations from Re:amaze with filtering and sorting. Common use cases: (1) Get oldest conversation waiting for response: {filter: "open", tag: "assigned-to-ben", sort: "updated", page_size: 10} then take LAST item in conversations array. (2) Get all open unassigned tickets: {filter: "unassigned"}. (3) Get all conversations for a customer: {for: "customer@example.com"}. Note: sort: "updated" returns NEWEST FIRST, so oldest conversation is at END of array.
Read Low risk
Get Customer
reamaze:get_customer
Execute get_customer action via reamaze
Read Low risk
Get Macros
reamaze:get_macros
Execute get_macros action via reamaze
Read Low risk
Merge Contact
reamaze:merge_contact
Merge duplicate customer profiles
Write Medium risk
Search Conversations
reamaze:search_conversations
Execute search_conversations action via reamaze
Read Low risk
Set Reminder
reamaze:set_reminder
Execute set_reminder action via reamaze
Write Low risk
Update Contact
reamaze:update_contact
Execute update_contact action via reamaze
Write Low risk
Update Conversation
reamaze:update_conversation
Update a Re:amaze conversation/ticket. Use this to assign tickets, change status, or update tags. CRITICAL: When cerebral cannot complete a task, use assignee_email to escalate to a human. Only provide fields you want to change - others remain unchanged.
Write Low risk
How it works

Every Re:amaze action
governed end-to-end.

Cerebral OS isn't a connector. It's the execution layer that sits in front of Re:amaze — adding governance, dry-run safety, and a full audit trail to every operation.

Governance first
Every verb carries a risk classification. High-risk writes require explicit approval gates before they execute in production.
Dry-run safe
Simulate any Re:amaze action before it touches production. See exactly what would happen before a single real call is made.
Immutable audit trail
Every Re:amaze action is logged — what ran, what changed, who approved it, when it happened. Full history on every verb, forever.
Re:amaze integration

16 actions.
Governed by default.

Connect Re:amaze to any workflow in minutes. Dry-run every action before it touches production. Full audit trail on everything.

Connect Re:amaze free Browse all integrations →