Meta tags:
description=Get and update draft email messages.;

Headings (most frequently used words):

email, messages, documentation, index, on, this, page, get, update, learn, api, cli, guides, concurrency, control, setting, content, git, workflow, flags,

Text of the page (most frequently used words):
email (29), lmx (19), the (17), #messages (13), file (12), revision (10), get (10), and (9), with (9), #update (9), loops (8), content (7), from (7), expected (6), force (6), draft (6), this (5), page (5), use (5), you (5), message (5), preview (4), text (4), subject (4), mutually (4), exclusive (4), current (4), contentrevisionid (4), api (4), contact (3), events (3), contacts (3), must (3), reply (3), name (3), before (3), automatically (3), fetch (3), concurrent (3), when (3), workflow (3), git (3), cmn5zia4i0017tzli8ric8giv (3), started (3), campaign (3), cli (3), workflows (3), are (2), last (2), flag (2), markup (2), inline (2), sender (2), overwrites (2), edits (2), flags (2), want (2), overwrite (2), latest (2), save (2), review (2), for (2), pass (2), setting (2), edit (2), concurrency (2), control (2), command (2), copy (2), emails (2), integrations (2), all (2), guides (2), transactional (2), search (2), documentation (2), index (2), support, responses, generated, using, may, contain, mistakes, assistant, linkedin, next, previous, yes, was, helpful, modified, july, 2026, least, one, provided, path, containing, address, username, part, team, sending, domain, appended, display, seen, description, short, only, intentionally, returned, making, another, commit, branch, run, your, repository, safer, based, any, prior, request, rejected, conflict, server, has, advanced, don, every, include, either, here, how, welcome, acme, clv8g2x4z012yl70n5o6p7q8r, fields, owning, status, including, its, keep, files, changes, locally, push, updates, protection, lets, view, attached, created, create, basics, recipes, creating, deliverability, getting, uploads, themes, lists, properties, components, completion, campaigns, auth, overview, changelog, webhooks, sdks, examples, reference, introduction, security, agent, skills, account, smtp, goals, editing, learn, navigation, log, home, skip, main, discover, available, pages, exploring, further, complete, docs, llms, txt,

Text of the page (random words):
email messages loops documentation index fetch the complete documentation index at docs llms txt use this file to discover all available pages before exploring further skip to main content loops home page contact us log in loops search navigation cli email messages search k learn get started editing emails workflows events goals contacts transactional email integrations smtp account agent skills for loops security api api introduction api reference examples sdks webhooks api changelog cli overview auth campaigns completion components contact properties contacts email messages events lists themes transactional uploads workflows guides all guides getting started workflows deliverability integrations creating emails recipes email basics on this page get update concurrency control setting content git workflow flags cli email messages copy page get and update draft email messages copy page the email messages command lets you view and edit the email message attached to a campaign email messages are created automatically when you create a campaign use this command when you want to keep email content in git as lmx files review changes locally and push updates to a draft email message with revision protection get get an email message by id including its current content and contentrevisionid loops email messages get cmn5zia4i0017tzli8ric8giv update update fields on a draft email message the owning campaign must be in draft status loops email messages update cmn5zia4i0017tzli8ric8giv expected revision id clv8g2x4z012yl70n5o6p7q8r subject welcome to acme preview text here s how to get started lmx file email lmx concurrency control every update must include either expected revision id or force expected revision id pass the contentrevisionid from a prior email messages get the request is rejected with a conflict if the server s revision has advanced so you don t overwrite a concurrent edit force fetch the current revision automatically and use it this overwrites any concurrent edits setting content pass lmx inline with lmx or from a file with lmx file loops email messages update cmn5zia4i0017tzli8ric8giv force lmx file email lmx git workflow for a safer file based workflow run loops email messages get email message id and save the current lmx in your repository commit the lmx file or review it in a branch update the draft email with lmx file and the latest expected revision id save the returned contentrevisionid before making another update use force only when you intentionally want to overwrite the latest draft content flags flag short description expected revision id r last seen contentrevisionid from email messages get mutually exclusive with force force f fetch the current revision and use it overwrites concurrent edits mutually exclusive with expected revision id subject email subject preview text email preview text from name sender display name from email sender username the part before the team s sending domain is appended automatically reply to reply to email address lmx lmx markup inline mutually exclusive with lmx file lmx file path to a file containing lmx markup mutually exclusive with lmx at least one content flag subject preview text from name from email reply to lmx or lmx file must be provided last modified on july 2 2026 was this page helpful yes no contacts previous events next i x linkedin assistant responses are generated using ai and may contain mistakes contact support