Every change to a record notifies the people following it. That is exactly what you want when a colleague updates a deal. It is exactly what you don't want when a nightly sync touches four hundred rows and everyone wakes up to four hundred notifications.
You can now mark a write as silent. Add "silent": true to the request body and that one write notifies nobody who follows the record:
curl -X POST https://infolobby.com/api/table/101/record/5/update \
-H "Authorization: Bearer il_live_..." \
-H "Content-Type: application/json" \
-d '{"data":{"status":"Synced"},"silent":true}'
It works on record create, update and delete, on comments, and on file attachments.
Quiet, not invisible
Silent mutes the broadcast to followers. It does not hide anything:
- Anyone you
@mentionin a comment is still notified. - Users newly assigned through a user field are still notified.
- The change still appears in record history and the activity feed.
- Your automations still run, exactly as they would on any other write.
So a silent write is safe for housekeeping without becoming a way to change data behind people's backs. If somebody needs to know, they still find out.
Everywhere you write
The same flag is available wherever InfoLobby writes data for you:
- The API, as above. See the records documentation.
- AI assistants connected through Claude or ChatGPT, or through the InfoLobby Skill. Tell your assistant to update the records quietly and it will.
- Automations, which have had this all along: tick Silent on a Create, Update, Delete, Add Comment or Generate PDF action.
Reach for it on syncs, backfills, imports from another system, and status stamps that nobody reads. Leave it off when the change is one a person should actually notice.