How to test emails from your Lovable application

1. 1
   Get your receiving address. After starting a subscription you choose a prefix, which gives you addresses of the form yourprefix+reference@in.demopost.net.
2. 2
   Put it in a test record. Set the email field of a test user, customer or contact in your application's data to that address. Use a different reference per scenario.
3. 3
   Trigger the sending flow your app already has — the signup, the order confirmation, the notification — through the app's own interface, so you test the real path.
4. 4
   Inspect the result in DemoPost: subject, sender, recipient, body, links and any attachment.

Note: this is the general recipient-based workflow. It does not depend on a DemoPost connector or on a specific setting inside Lovable, and we do not claim to have tested your particular project's configuration.

• Your app is actually configured to send email — a form that only writes to the database sends nothing, and no test inbox will change that.
• The environment you triggered is the one you configured, not a different deployment.
• The recipient stored on the test record is the DemoPost address, spelled exactly, plus sign included.
• The flow ran to completion without a server error.
• The message content matches the record you created, and links point at the right environment.

Start at the sending side

Check your provider's own logs or dashboard first: if there is no outgoing message there, the problem is in your application or its configuration, and DemoPost has nothing to receive. Common causes are a missing API key in the deployed environment, a sending domain that is not verified yet, a provider in test mode that only delivers to verified addresses, or the function that should send never being reached.

Then check the address

A typo in the prefix, a stripped plus sign, or an old address left on the test record will all produce silence. Copy the address from your DemoPost workspace rather than typing it.

Then wait a little

Queues can delay delivery by a few minutes. Use the refresh button before concluding the message is lost, and check whether the provider reports a bounce or a rejection.