[wstrinz]

Addresses: GG-1952

Documents changes here:

• https://github.com/DripEmail/drip/pull/31853

TL;DR

Documents GET /v2/:account_id/workflows/:workflow_id/emails/:workflow_email_id, and the email object on send_email nodes in workflow details.

Background

drip#31853 added a way to read a workflow email's subject, preheader and bodies over the API, and added email: {id, subject} to send_email action nodes in the workflow details response. Neither is in the public docs yet.

Modification

In source/includes/rest/_workflows.md:

• New "Fetch a workflow email" section after "Fetch a workflow's details": request examples (cURL, Ruby, JavaScript, in the same style as the details section), an example response, a properties table, and the 404 a mismatched email id returns.
• Workflow details: the example send_email step now shows email, the node table lists it for actions, and a paragraph explains email.id versus properties.automation_email_id.

Field names and wording come from drip's docs/api/v2/workflow_emails_api_spec.yaml, the workflow_emails/show.json.jbuilder view, and the details serializer.

Result

The endpoint and the new details field appear on developer.drip.com after the next deploy.

How to verify/test in production

After make deploy, open https://developer.drip.com/#fetch-a-workflow-email and check that the section renders with its three language tabs, and that the "Fetch a workflow's details" link from it jumps to the details section.

Checklist

• The PR title contains the JIRA key (if using JIRA).
• You have manually tested/validated your changes (if applicable).
• Automatic tests and/or monitoring have been added or updated. (n/a: CI builds the site)
• Full PR template above has been filled in.

🤖 Generated with Claude Code