Short answer: You can update one mongodb document in MongoDB Atlas by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the MongoDB Atlas Update One MongoDB Document action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 | – |
Filter filter | object | Required | Find the document to update. Most common: `{"_id": "abc"}` or `{"email": "x@y.com"}`. |
Update update | object | Required | Update operators. e.g. `{"$set":{"name":"new"}}`, `{"$inc":{"count":1}}`. |
Upsert upsert | boolean | Optional | If true, insert if no match. |
{"database": "{{trigger.database}}","collection": "{{trigger.collection}}","filter": "{{trigger.filter}}","update": "{{trigger.update}}","upsert": "{{trigger.upsert}}"}
{"upsertedId": null,"matchedCount": 1,"modifiedCount": 1}
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.