Event hooks
Event hooks run automatically when something important finishes, without relying on chat to remember a follow-up. You describe the journey (after submit, notify; after done, create the related record). GenieForge wires the trigger and follow-up. Find hooks under App Blueprint → Event Hooks. Typical sources include tool success, record create/update, form submit, scheduled job complete, invite, or registration. Hooks are blueprint configuration; they run in the project where the event occurred.How to verify
- Find hooks under App Blueprint → Event Hooks.
- Trigger the source action in Preview as the right role (or Run Now on a related automation).
- Confirm the follow-up in project data, email/inbox, and Executions.
- If a hook fails, fix the follow-up and re-trigger; the original action should not have been undone.
Limits and notes
- Follow-ups should be safe to retry. A failed welcome email must not imply the invite never happened.
- Chat is a bad place to “remember” operational follow-ups. Prefer durable automations GenieForge already maintains for that outcome.
- After a change, re-check the path that should fire the follow-up before you treat the version as live.