Base44 Introduces Hooks to Allow or Block App Actions
Base44Base44 introduced Hooks, a new workflow type that runs just before an app action and either allows or blocks it. Uses include protecting data changes, controlling signups and sign-ins, deciding who can use built-in integrations and giving in-app agents context. Hooks are created by describing a rule in the AI chat and are rolling out gradually.
Key Takeaways
- Hooks run before an app action and either allow or block it.
- They are a new workflow type, living in the Workflows page.
- Typical uses: protecting data changes and controlling signups and sign-ins.
- Hooks can also decide who may use built-in integrations.
- They can give in-app agents extra context.
- Rules can be created by describing them to the AI chat; rollout is gradual.
A Workflow That Runs Before an Action
Hooks are a new type of workflow. Instead of reacting after something happens, a hook runs immediately before an app action and decides whether the action may proceed. This gives builders a place to enforce their own rules.
What Hooks Can Be Used For
Base44 lists several uses: protecting data changes, controlling signups and sign-ins, deciding who can use built-in integrations, and giving in-app agents extra context.
Creating a Hook
A hook can be created by describing the rule to the AI chat in plain language, or from the Hooks section of the Workflows page.
Availability
Hooks are rolling out gradually, so not every workspace sees them yet.
Why It Matters
Until now, workflows mostly responded to events. Hooks add a gating layer, so builders can validate or reject actions without writing custom server code.