Short answer: Drop the "MongoDB Atlas → Find MongoDB Documents" 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 | myapp_prod |
Collection collection | string | Required | users |
Filter filter | object | Optional | MongoDB query filter. `{}` returns all. Use operators: `{"status":"active"}`, `{"age":{"$gt":18}}`, `{"tags":{"$in":["a","b"]}}`. |
Projection projection | object | Optional | Fields to include/exclude: `{"_id":1, "name":1}` or `{"password":0}`. |
Sort sort | object | Optional | `{"created_at":-1}` for desc, `1` for asc. |
Limit limit | number | Optional | Max documents to return (Data API cap is 1000). |
Skip skip | number | Optional | Offset for pagination. |
{"database": "myapp_prod","collection": "users","filter": "{{trigger.filter}}","projection": "{{trigger.projection}}","sort": "{{trigger.sort}}"}
{"documents": [{"_id": "6a02b...","name": "Jane","email": "jane@example.com"}]}
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.