Project deleted
Lovable sends an automated notice to your secure web address whenever a project is deleted. This notification fires immediately upon soft deletion, and no second message is sent if the project is later permanently erased.
Anyone integrating external services who needs to clean up records or trigger actions when a Lovable project gets deleted.
Do this, in order
- 1
Create an HTTPS endpoint in your backend to accept incoming webhook POST requests.
Lovable requires a secure destination URL to deliver project event notifications.
- 2
Add signature verification logic using your webhook secret before processing incoming payloads.
Verification guarantees the notification genuinely originated from Lovable and has not been altered.
- 3
Handle the project.deleted.v1 event payload to remove or archive corresponding records in your systems.
This event triggers immediately upon deletion so external databases stay in sync.
Paste this into your project
Create an API route in my app to receive incoming Lovable webhooks. Add signature verification logic to validate incoming requests, and add a handler for the project.deleted.v1 event that logs the deletion and updates the local project record status.
Words decoded
- HTTPS endpoint
- A secure web address hosted on a server that receives incoming data from other services.
- Webhook
- An automated notification sent between computer systems in real time when an event occurs.
- Soft deletion
- Marking an item as deleted or moving it to a trash state without permanently erasing it immediately.
Where people get stuck
- Expecting another event during a hard purge: Lovable only emits a notification on initial soft deletion, not when permanently wiped later.
- Failing to verify webhook signatures, which allows unauthorized parties to send fake deletion events to your endpoint.
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.