Hookified

Hookified is a decentralized automation platform that lets users create, run, and manage “hooks” small automated workflows that connect onchain and offchain events to actions. Think of it as “Zapier for Web3”: a reliable, no-code way to respond to blockchain activity (like token transfers or contract events) or time-based schedules and trigger offchain integrations (such as Telegram, webhooks, or analytics) or onchain actions (like smart contract calls). All of this happens while keeping user keys secure through Lit Protocol.

Users can define a Hook as a simple Trigger → Action flow. Triggers can be things like an onchain event, a wallet activity, a cron schedule, or an incoming webhook. Actions can include sending a Telegram alert, calling an API, triggering another Hook, or executing a smart contract function. Hookified watches for triggers, runs the appropriate actions, and logs results, giving users visibility and control over their automations. It also includes a Hooks Registry where users can copy and modify prebuilt hooks to get started quickly.

The platform bridges Web3 and Web2, removing the need for developers to write custom scripts or monitor nodes. It empowers DAOs, DeFi teams, and community managers to automate blockchain operations safely and easily. With Lit Protocol, users can securely create or import wallets, with private keys encrypted client-side and never exposed to the backend.

From a technical standpoint, Hookified uses Next.js for both frontend and backend, Supabase for authentication, storage, and database, and Prisma for structured database access. The Trigger Engine runs in background jobs using Supabase’s cron functionality. It listens to blockchain events (via Base RPCs or APIs), matches them to user-defined triggers, and executes actions via modular adapters (Telegram, Webhooks, etc.). All executions are logged in HookRun records, which track success, failure, and retries.

The architecture includes:

• Frontend: Next.js + Supabase for auth, Lit SDK for wallet encryption.
• Backend: Next.js API routes + Prisma ORM.
• Database: Supabase Postgres with tables for Users, Wallets, Hooks, HookRuns, and Templates.
• Workers: background services to detect events and execute hooks.
• Adapters: pluggable modules for new triggers or actions.
• Security: keys encrypted by Lit Protocol and never handled in plaintext by the server.

The MVP includes:

• User sign-up/login.
• Wallet creation/import with Lit encryption.
• Hook creation and management.
• Triggers (onchain + cron).
• Actions (Telegram notifications).
• Hooks Registry for prebuilt templates.
• Execution logs and error tracking.

Future expansions include more trigger types (price, balance, webhooks), more action integrations (email, contract calls, Discord), and a marketplace for user-created templates.

Hookified’s value lies in making blockchain automation accessible, secure, and fast. It saves time for developers, gives non-technical users a way to automate workflows without coding, and builds a trusted foundation for future automation infrastructure in Web3.

Hookified was built using a modern full-stack setup centered around Next.js and Supabase, with a focus on speed, modularity, and security. The goal was to deliver a production-ready MVP that could demonstrate real onchain automation while staying lightweight enough to build and iterate quickly.

At the core, Next.js powers both the frontend and backend APIs. The frontend is a responsive dashboard where users can sign up, connect or create wallets, and configure hooks. The backend API routes handle user data, hook management, and interaction with Supabase and blockchain nodes. Prisma acts as the ORM layer for database interactions, ensuring structured access and schema consistency.

For authentication, database, and file storage, we used Supabase. It also serves as our provider for background jobs (via Supabase Cron), which periodically run the Trigger Engine. The Trigger Engine listens to blockchain events and time-based triggers, checking if any active hooks match the conditions. When it finds one, it executes the defined actions (like sending a Telegram message or firing a webhook).

The blockchain side runs on Base, where we fetch and decode onchain logs using RPC and event filters. For signing and secure wallet operations, we integrated Lit Protocol, which was a key differentiator. Users can create or import wallets, and the private keys are encrypted client-side using Lit’s distributed encryption. The app only stores encrypted key references, never the keys themselves, providing a much safer setup for onchain automations.

The Hookified system is modular each trigger and action is an adapter. This made it easy to add new integrations quickly during development. For example, the Telegram action adapter simply formats event data and calls Telegram’s API. Each hook run is logged in Supabase with status, metadata, and retries for reliability.

A few hacky but effective solutions were implemented to move fast:

• Instead of deploying a separate worker system, we leveraged Supabase’s scheduled functions to simulate cron jobs for the Trigger Engine, letting us keep all logic in the same codebase.
• We used Next.js API routes both for serving UI data and as internal endpoints for hook execution, which simplified deployment and reduced infra overhead.
• The registry templates were generated as JSON definitions instead of being stored as code files, allowing instant updates and reuse without redeployment.

Overall, Hookified is a combination of solid full-stack engineering and creative use of partner technologies. Supabase provided a reliable backend foundation, Base gave us a performant blockchain to monitor, and Lit Protocol solved secure key management in a truly decentralized way. The result is a working automation platform that securely connects Web3 and Web2 in real time.