For Admins
Log from Flow and Process Builder with zero code, using Nebula Logger's invocable actions.
You don’t need to write Apex to get observability into your automations. Nebula Logger ships four invocable actions that drop straight into Flow Builder.
The four invocable actions
Add Log Entry
Log a plain message from anywhere in a Flow.
Add Log Entry for a Record
Log a message tied to a specific SObject record.
Add Log Entry for a Record Collection
Log one message against a whole collection of records in a loop-free way.
Save Log
Persist everything logged so far in this Flow interview.
Why admins care
Flows fail silently more often than anyone would like — a bad record update, a failed callout, an unmet entry condition. Wiring in a Save Log action at key decision points turns “the Flow just didn’t work” into a queryable Log__c record your team can actually look at, filter, and report on.
Tagging from Flow
Tags don’t require Apex either — specify a comma-separated list directly in the Tags input of any logging action, for example billing, retry-eligible. See Tagging & Data for how tags and custom metadata rules work together.
Where the data lives
Every Flow log entry lands in the same Logger Console app as Apex and LWC logs — no separate admin tooling to learn. From there you get list views, a related-records component for record pages, and a JSON view for anything that needs deeper inspection.