FAQ
Transferring leads from landing page builders such as Tilda, LPgenerator, Flexbe, Wix and etc
Albato
Sending Leads from a Tilda Landing Page to onecrypt.link via Albato
Prerequisites
Before you begin, make sure you have the following:
The setup consists of four parts:
Before you begin, make sure you have the following:
- An Albato account (the instructions below use the Russian-language interface).
- Access to your Tilda website admin panel with permission to edit website settings and forms.
- Your API key from your onecrypt.link profile: https://onecrypt.link/u/profile (under the API tab).
- The Offer ID of the affiliate offer associated with this landing page.
The setup consists of four parts:
- Configure Albato to receive lead data submitted through your Tilda form (Parts 1–2).
- Configure Albato to send that data to onecrypt.link (Part 3).
- Connect both steps into a single automated workflow (Part 4).
Part 1. Configuring Lead Reception from Your Website — Webhook Connection
Step 1. Create a Webhook Connection in Albato
First, create a Webhook connection. This webhook will act as the endpoint that receives lead data submitted through your landing page form.
In Albato, go to the Connections tab and select Webhook from the list of available services.
Step 1. Create a Webhook Connection in Albato
First, create a Webhook connection. This webhook will act as the endpoint that receives lead data submitted through your landing page form.
In Albato, go to the Connections tab and select Webhook from the list of available services.
Step 2. Copy the Webhook URL and Enable Listening Mode
Enter a descriptive name for the connection (for example, "Webhook – [Landing Page Name]"), then copy the Webhook URL from the Webhook settings. This is the endpoint where Tilda will send your form submission data.
Next, click Catch Webhook. Albato will enter listening mode and wait for an incoming request. As soon as a form is submitted from your landing page, Albato will capture and display the received data.
Enter a descriptive name for the connection (for example, "Webhook – [Landing Page Name]"), then copy the Webhook URL from the Webhook settings. This is the endpoint where Tilda will send your form submission data.
Next, click Catch Webhook. Albato will enter listening mode and wait for an incoming request. As soon as a form is submitted from your landing page, Albato will capture and display the received data.
⚠️ Important: Do not close this Albato tab. You’ll need it in the next few steps to verify that the form data has been received successfully.
Part 2. Configuring Data Reception in Tilda
Step 3. Open Your Website Settings
Without closing the Albato page, switch to Tilda and open the Site Settings for the landing page you want to connect.
Step 3. Open Your Website Settings
Without closing the Albato page, switch to Tilda and open the Site Settings for the landing page you want to connect.
Step 4. Go to Forms → Webhook
In the Site Settings, open the Forms tab and select Webhook. This is Tilda's built-in integration for sending form submission data to an external endpoint.
In the Site Settings, open the Forms tab and select Webhook. This is Tilda's built-in integration for sending form submission data to an external endpoint.
Step 5. Paste the Webhook URL and Connect the Service
Paste the Webhook URL you copied in Step 2 into the WEBHOOK URL field.
Then click Connect the service to all forms on the site so that every form on the website sends its submissions to Albato.
Finally, save your changes.
Paste the Webhook URL you copied in Step 2 into the WEBHOOK URL field.
Then click Connect the service to all forms on the site so that every form on the website sends its submissions to Albato.
Finally, save your changes.
Step 6. Saving Changes
Step 7. Republish the Landing Page
Open the landing page containing the form and click Publish to apply the changes.
Open the landing page containing the form and click Publish to apply the changes.
⚠️ Important: This step is mandatory. If you don't republish the page, the form will continue using its previous configuration and will not send submissions to Albato, even if the Webhook settings have been saved.
Step 8. Verify That Albato Receives the Data
Open the published version of your landing page (not the editor preview) and submit the form using test data.
If everything is configured correctly, the Catch Webhook page in Albato (opened in Step 2) will immediately display a notification along with the list of fields received from the form (such as Name, Phone, Email, etc.).
This confirms that the inbound webhook has been configured successfully and Albato is receiving form submissions from your landing page.
Open the published version of your landing page (not the editor preview) and submit the form using test data.
If everything is configured correctly, the Catch Webhook page in Albato (opened in Step 2) will immediately display a notification along with the list of fields received from the form (such as Name, Phone, Email, etc.).
This confirms that the inbound webhook has been configured successfully and Albato is receiving form submissions from your landing page.
Part 3. Configuring Lead Delivery to onecrypt.linkStep 9. Create an HTTP Request Connection
Go back to the Connections tab in Albato and create a new HTTP Request connection.
Unlike the Webhook connection, which receives incoming data, the HTTP Request connection is used to send lead data to an external endpoint—in this case, onecrypt.link.
Go back to the Connections tab in Albato and create a new HTTP Request connection.
Unlike the Webhook connection, which receives incoming data, the HTTP Request connection is used to send lead data to an external endpoint—in this case, onecrypt.link.
Step 10. Configure the onecrypt.link Lead Endpoint
Give the connection a descriptive name (for example, "Send Lead to onecrypt.link") and enter the following endpoint in the URL field:
http://api.onecrypt.link/api/lead/send
In the Content-Type field, make sure to select JSON. Our API accepts request data only in JSON format and does not support the default application/x-www-form-urlencoded format.
Give the connection a descriptive name (for example, "Send Lead to onecrypt.link") and enter the following endpoint in the URL field:
http://api.onecrypt.link/api/lead/send
In the Content-Type field, make sure to select JSON. Our API accepts request data only in JSON format and does not support the default application/x-www-form-urlencoded format.
Part 4. Building the Complete Automation
Step 11. Add an Action to the Webhook Workflow
Go to the My Automations tab in Albato and open the workflow containing the webhook you configured in Parts 1–2.
Click Add Action to create the next step in the automation.
Step 11. Add an Action to the Webhook Workflow
Go to the My Automations tab in Albato and open the workflow containing the webhook you configured in Parts 1–2.
Click Add Action to create the next step in the automation.
Step 12. Select Send Request
For the action type, select Send Request.
Then, in the second field, choose the HTTP Request connection you created in Steps 9–10.
Click Continue to proceed.
For the action type, select Send Request.
Then, in the second field, choose the HTTP Request connection you created in Steps 9–10.
Click Continue to proceed.
Step 13. Select the Request Method
Click the HTTP Request action you just added to open its configuration panel.
Set the request method to POST. Be sure to use POST, not GET.
Click the HTTP Request action you just added to open its configuration panel.
Set the request method to POST. Be sure to use POST, not GET.
Step 14. Configure the Request Parameters
In the request parameters, specify the following:
In the request parameters, specify the following:
- Your API key from your onecrypt.link profile.
- The Offer ID.
- The offer's target country.
- The IP address.
⚠️ Why the IP address is set to 0.0.0.0: Tilda does not send the form data directly from the visitor's browser. Instead, it forwards the submission through its own server using a server-to-server connection. As a result, the visitor's real IP address is not available in the webhook payload. The value 0.0.0.0 is used as a temporary placeholder for the required ip_address field.
⚠️ Important: In addition to the static parameters (key, offer_id, country, and ip_address), make sure the request also includes the dynamic fields mapped from the webhook data. At a minimum, map phone, which is required by the API specification, as well as name and email if those fields are collected by the form. Otherwise, onecrypt.link will receive leads without the lead's contact details.
⚠️ Important: In addition to the static parameters (key, offer_id, country, and ip_address), make sure the request also includes the dynamic fields mapped from the webhook data. At a minimum, map phone, which is required by the API specification, as well as name and email if those fields are collected by the form. Otherwise, onecrypt.link will receive leads without the lead's contact details.
Required fields according to the onecrypt.link API specification: key, offer_id, phone, and ip_address. A lead submission will be rejected if any of these fields are missing.
Save the request parameter settings.
Save the request parameter settings.
Final Verification
The integration is now complete.
Submit your form once again using test data. The lead should be successfully delivered to the onecrypt.link affiliate platform.
Verify the integration at each stage:
The integration is now complete.
Submit your form once again using test data. The lead should be successfully delivered to the onecrypt.link affiliate platform.
Verify the integration at each stage:
- In Albato: Open the automation execution history. Both steps (Webhook and HTTP Request) should complete successfully without errors. The HTTP Request step should return HTTP 200 along with a JSON response containing the lead id.
- In onecrypt.link: Ask your team to verify, or check yourself, that the test lead appears in the Leads section of the affiliate dashboard.
- If everything works as expected, you can leave the automation enabled to process leads continuously.
Common Issues
The lead does not reach Albato
Make sure the landing page was republished after connecting the Webhook (see Step 7).
The lead reaches Albato but not onecrypt.link
Verify that:
Ensure that the ip_address parameter is set to 0.0.0.0 (or another value approved by onecrypt.link), rather than being left empty or populated with Tilda's or Albato's server IP address.
The lead is received without a phone number or name
The lead does not reach Albato
Make sure the landing page was republished after connecting the Webhook (see Step 7).
The lead reaches Albato but not onecrypt.link
Verify that:
- the endpoint URL is entered correctly (without typos);
- the request method is set to POST;
- the Content-Type is set to JSON.
Ensure that the ip_address parameter is set to 0.0.0.0 (or another value approved by onecrypt.link), rather than being left empty or populated with Tilda's or Albato's server IP address.
The lead is received without a phone number or name
- Check that these fields are correctly mapped in the request parameters (see Step 14) to the corresponding dynamic fields from the webhook payload, rather than being left empty.