Learn to build Event Listeners that configure and customize Flatfile through hands-on coding tutorials
space:configure
job, and may be as simple as logging an Event to the console, or as complex as processing records against existing data from your own API. But given the Event/Listener pattern as basic building blocks, you can build pretty much anything your imagination can conjure.
This event-driven paradigm is fundamentally different from traditional “configuration”, where you pre-define static options. Instead, you write reactive code that responds to what users actually do. Events carry structured information about what happened, including the context and any relevant data, giving your Listeners everything they need to respond intelligently.
Common Events include:
commit:created
- When a commit is created (after records are added or modified)job:ready
- When Jobs are ready for executionfile:created
- When a file is uploadedcommit:created
Events and perform your validation in the callback. Need to process uploaded files? Listen for file:created
Events. Want to trigger discrete units of work? Listen for job:ready
Events (generally filtered by {job: "domain:operation"}
, but we’ll cover that later).
For a more comprehensive understanding of this topic, see Events and Listeners.