Skip to main content

current_record_comment_or_reply_reply_create

Internal beta โ€” config shape is being migrated

The Automation API is an internal beta and is not released yet โ€” endpoints and payloads may change or be withdrawn without notice. This action's config is being migrated to a typed schema; the fields below reflect that in-progress shape. Always read the authoritative, live shape from GET /v1/automation/meta/action before building against it.

Add reply โ€” posts a reply to the comment or reply that triggered the automation. group: "action". Requires the record_comment_or_reply_created trigger context.

Part of the Current record family. This page documents the typed config; for how an action sits inside an automation definition, see Actions and Action examples.

Configโ€‹

KeyTypeRequiredDescription
reply_contenttemplate valueyesReply body.
author_idinteger | referencenoUser the reply is attributed to โ€” a literal user id or a variable reference. Omitted โ†’ the automation itself.
trigger_webhooksbooleannoWhether the reply fires outbound webhooks.
trigger_other_flowsbooleannoWhether the reply triggers other automations.
silentbooleannoWhether the reply is silent (suppresses notifications).

Exampleโ€‹

An action entry inside an automation definition's actions[]:

{
"type": "current_record_comment_or_reply_reply_create",
"config": {
"reply_content": ["Thanks โ€” logged by ", { "kind": "variable", "source": "meta", "meta_type": "app_record_id" }],
"silent": true
}
}

Validation & behaviorโ€‹

  • reply_content is the only required member โ€” it has no canonical default; every other member is an optional mutation control.
  • The action needs the record_comment_or_reply_created trigger context: it replies to the comment or reply that fired the automation.
  • With author_id omitted, the reply is attributed to the automation itself.
  • trigger_webhooks, trigger_other_flows, and silent are omitted by default and fall back to the internal defaults for the mutation.

See alsoโ€‹