Short answer: Drop the "MongoDB Atlas → Insert One MongoDB Document" 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 |
|---|---|---|---|
Database database | string | Required | — |
Collection collection | string | Required | — |
Document document | object | Required | JSON document to insert. Atlas auto-assigns `_id` if omitted. |
{"database": "{{trigger.database}}","collection": "{{trigger.collection}}","document": "{{trigger.document}}"}
{"insertedId": "6a02b1f5c0e8b34d2a9c1234"}
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.