Connect your app to Inngest
You can connect your Lovable app to Inngest to add background jobs, scheduled tasks, and multi-step workflows. This lets your app do things like send delayed notifications, process data on a schedule, or handle complex tasks outside of immediate user requests.
Anyone building a Lovable app who needs to run tasks in the background, on a schedule, or as part of a multi-step process that might take a while.
Do this, in order
- 1
Go to 'Connectors' in your Lovable workspace and choose 'Inngest'.
This is where you manage all connections to other services for your Lovable projects.
- 2
Click 'Add connection'.
You need to create a new connection to Inngest using your own account details.
- 3
Give your connection a clear name, like 'Inngest Production' or 'Inngest Staging'.
A descriptive name helps you easily identify what this connection is for, especially if you have multiple Inngest setups.
- 4
Paste your Inngest Event Key and Signing Key into the provided fields.
These keys are your personal credentials that allow Lovable to securely communicate with your Inngest account. You can find them in your Inngest dashboard under 'Settings -> Keys'.
- 5
Click 'Create'.
This saves your Inngest connection and makes it available for use across projects in your Lovable workspace.
- 6
In your Lovable project chat, ask Lovable to create background jobs or scheduled workflows that use Inngest.
Once connected, you can prompt Lovable to build features that leverage Inngest's capabilities, like sending a welcome email days after signup or generating a weekly report.
- 7
Trigger an event in your app that should use Inngest, then check your Inngest dashboard to confirm the function runs.
This verifies that your Lovable app is successfully sending tasks to Inngest and that Inngest is processing them as expected.
Paste this into your project
I need to add background jobs and scheduled tasks to my app. I've already connected Inngest using my Event Key and Signing Key. Can you help me set up a workflow to [describe your specific workflow, e.g., 'send a welcome email immediately after a user signs up, then a follow-up email 3 days later']?
Words decoded
- Background jobs
- Tasks that run behind the scenes without directly interrupting the user, like sending an email after a purchase.
- Scheduled tasks
- Tasks that run automatically at specific times or intervals, such as generating a report every Monday morning.
- Durable workflows
- Multi-step processes that can pause and resume, remember their state, and automatically retry if something goes wrong, like a series of actions after a user signs up.
- Event-driven workflows
- Workflows that start when a specific 'event' happens, like a user signing up or a new data record appearing.
- Workspace-level connection
- A single connection to an external service that can be shared and used by all projects within your Lovable workspace, rather than needing a separate connection for each project or user.
- Inngest Event Key
- A secret code that identifies your Inngest account when sending new events or tasks to it.
- Inngest Signing Key
- A secret code used to verify that events sent to Inngest are legitimate and come from your authorized Lovable app.
- Cron expressions
- A special code used to define schedules for tasks, like '0 9 * * 1' which means 'every Monday at 9 AM'.
Where people get stuck
- You must have your own Inngest account and API keys; Lovable does not provide them.
- Function runs are billed by Inngest, not Lovable, based on your Inngest plan.
- App + chat connector connections are shared across your entire Lovable workspace, meaning anyone with access to connected projects can use the Inngest connection.
- You cannot use this connector if each end user needs to connect their own Inngest account separately.
- If your app stops triggering events after changes, always re-check your connection settings to ensure it's still linked correctly.
- Inngest functions are managed and monitored directly in the Inngest dashboard, not within Lovable.
The short version, steps, decoder and prompt on this page are written automatically from Lovable's own documentation and can lag or misread it. The official page is always the authority.