Project transferred to another workspace

1. 1

   Set up an Events & Hooks subscription in your workspace with your secure HTTPS endpoint.

   Lovable needs an active destination address to deliver event notifications.

2. 2

   Verify the incoming signature on the notification request before processing it.

   This ensures the request genuinely came from Lovable and has not been altered.

3. 3

   Inspect the workspace_id field in the received payload to identify which workspace received the delivery.

   Both the sending and receiving workspaces get notifications sharing the same event ID, so the workspace ID indicates which side you are reading.

Create an API endpoint that receives Lovable webhook requests, verifies the incoming request signature, and handles the project.workspace_transferred.v1 event by logging the event ID and the associated workspace ID.

HTTPS endpoint

A secure web address on your server designed to receive data automatically from external services.

Event ID

A unique identifier assigned to a specific occurrence so related notifications can be matched together.

Signature verification

A cryptographic check to prove that a received message is authentic and untampered.

• Assuming only the receiving workspace gets notified; both the source and destination workspaces receive deliveries sharing the same event ID.
• Failing to verify request signatures, leaving your webhook endpoint open to spoofed data.
• Expecting immediate read consistency after a transfer, since workspace project lists may take a brief moment to reflect the change.