New connectors: Unbounce, Instapage and Nuvemshop

Two more landing page form capturers (Unbounce and Instapage) and one more e-commerce platform (Nuvemshop / Tiendanube), all in the bring-your-own-account (BYO) model. Paste the credential in Settings, Integrations, enable it, and only then do they work. Credentials encrypted, no cost on our side.

These connectors follow the same model as the others: you bring your own account (BYO). Open Settings, Integrations, find the card, paste the credential (always encrypted) and enable it. Until it is configured and enabled, nothing happens. There is no cost, margin, or middleman on our side.

Landing pages: Unbounce and Instapage

They turn each landing page form submission into a Lead, with the same flexible field matching (name, email, phone, company, message) as Typeform and Google Forms. There is deduplication by email and by submission id.

1. Unbounce: on your landing page form, add a submission webhook pointing to the card URL. Optionally set a shared secret (sent in the X-Unbounce-Secret header or a secret field) to strengthen verification.
2. Instapage: on your landing page, add the Webhook integration pointing to the card URL. Optionally set the same kind of shared secret.
3. Enable it. Each identifiable submission becomes a Lead. Neither one signs the calls natively, so security relies on the unpredictable URL token (plus the shared secret, if you set one).

E-commerce: Nuvemshop / Tiendanube

It syncs your Nuvemshop (Tiendanube) store into the CRM: each customer becomes a Contact and each order becomes a Sales order. As with BigCommerce, the Nuvemshop webhook carries only the resource id, so the CRM fetches the details from the Nuvemshop API with your access token before syncing. The sync is idempotent: a webhook redelivery does not duplicate records.

1. In the Nuvemshop app panel, get the store ID (store_id), the app secret (client secret) and an access token with read access to Customers and Orders.
2. On the E-commerce (Nuvemshop / Tiendanube) card, fill in these three values and save. Copy the webhook URL that appears.
3. In Nuvemshop, register customer and order event webhooks pointing to that URL. Each delivery is signed with your app secret (HMAC-SHA256, x-linkedstore-hmac-sha256 header), which the CRM verifies before syncing.
4. Enable it. Handled events: customer/created, customer/updated, order/created, order/updated, order/paid, order/cancelled and order/fulfilled.

If a webhook is rejected, check the secret (a value different from the one saved in the CRM is rejected with 401). In Nuvemshop, without the access token the CRM cannot fetch the resource details and the event is safely ignored.

Open this article inside the system →