Short answer: Drop the "LinkedIn → Comment on LinkedIn Post" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Post URN post_urn | string | Required | urn:li:share:71... |
Actor URN (commenter) actor_urn | string | Required | — |
Comment Text message | string | Required | — |
{"post_urn": "urn:li:share:71...","actor_urn": "{{trigger.actor_urn}}","message": "{{trigger.message}}"}
{"id": "urn:li:comment:..."}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.