Content & Images
Reusable message and image templates, and the sender personas outreach is written as.
Content is the reusable half of outreach. A template holds the channel, the copy rules and the prompt; a campaign run turns it into concrete drafts addressed to real people. Images work the same way — a reusable seed lives on the template, and the generated image lands on the draft.
Create a template
Create a content — POST /api/v1/content
curl -X POST "https://moabcrm.com/api/v1/content" \
-H "Authorization: Bearer $DASH_API_KEY" \
-H "Project-ID: pr_zest" \
-H "Content-Type: application/json" \
-d '{"name":"Acme introduction","type":"email","mode":"template","product_id":"$PRODUCT_ID","subject_template":"A question about your review workflow","body_template":"Hi {{first_name}} — Acme helps teams review pull requests. Would a short demo be useful?","status":"paused"}'Write a new email template about the Hermes launchdata_set {
"collection": "content",
"object_id": "draft-001",
"data": {
"name": "Acme introduction",
"type": "email",
"mode": "template",
"product_id": "$PRODUCT_ID",
"subject_template": "A question about your review workflow",
"body_template": "Hi {{first_name}} — Acme helps teams review pull requests. Would a short demo be useful?",
"status": "paused"
}
}{
"object": "content",
"id": "obj_123",
"name": "Hermes joins the team",
"type": "email",
"mode": "template",
"status": "live",
"score": {
"total": 8,
"components": [
{
"id": "best_practices",
"kind": "best_practices",
"points": 5,
"note": "+ plain-subject, template-has-image, new-angle, grounded-body, cta-block-correct"
},
{
"id": "signups",
"kind": "signups",
"points": 3,
"note": "3 attributed signups"
}
]
},
"channel": "channel",
"content_prompt": "content prompt",
"subject_template": "A question about your review workflow",
"headline": "headline",
"body_template": "Hi {{first_name}} — Acme helps teams review pull requests. Would a short demo be useful?",
"body": "body",
"best": true,
"has_offer": true,
"image": {
"source": "source",
"source_url": "source url",
"alt_text": "alt text",
"scope": "scope"
},
"public_asset": {
"url": "https://example.com",
"mime_type": "mime type",
"width": 1,
"height": 1
},
"created_at": "2026-07-25T12:00:00.000Z",
"updated_at": "2026-07-25T12:00:00.000Z"
}The resources
content— reusable message and image templates.employees— the sender personas outreach is written as;voice_mdandsignatureare yours to edit.artifacts— read-only. Files and images a run produced or you uploaded.
Each reference page lists the fields you can send, the read-only fields that come back, and the filters and sort keys the endpoint serves.
Worth knowing
- Content work never sends. Every draft a template generates starts as
status: "draft"; approval is a separate, human step — see Outbox. - Image linkage spans two objects: the reusable seed is
content.seed_artifact_id, and each generated output image isoutbox.image_artifact_id. public_asset.urlis for published assets only — a stable, email-safe, absolute HTTPS JPEG or PNG. If nothing is published, the message ships without an image rather than with an invented URL.- Never write
slug. The server derives it fromname/object_id. artifactsis read-only over REST — upload withartifacts_upload, or just drop the file in the chat.- The approval brake can hold an autonomous run before it writes anything — see Control plane. Reads and edits are never gated.
Let the agent do it
Hand over the bytes and one sentence;
write-content owns what good Moab content looks
like, including whether a template already covers it.
artifacts_upload { "project_id": "pr_zest", "filename": "shot.png",
"mime_type": "image/png", "content_base64": "…" } // → { artifact: { id } }
tasks_create { "project_id": "pr_zest", "skill_id": "write-content", "run": true,
"artifact_ids": ["art_…"], "input": { "seedArtifactId": "art_…" },
"prompt": "<the operator's sentence, verbatim>" }
tasks_status { "task_id": "ts_…" } // → content id, agent id, draft countNext: Approve your content, then Outbox.