Connect the tools your business uses

A booking link sends the visitor to an external service. An embed displays that service within the website. A service connection can send a supported request with a private key.

Ask Launch for the business result and name the service. A website button does not by itself create a completed payment or confirmed booking.

1. Describe the visitor action and the expected result.
2. Use the service's official link, embed instructions, or integration documentation.
3. Check the action in Preview when supported, then on the live site.
4. Confirm the resulting record in the destination service.

Site overview → Custom code provides Head code and Footer code. Each snippet applies to every page on the next publish.

Custom code runs only on the connected custom domain. Launch switches it off on the webrenew.app address.

1. Copy the official snippet intended for a public website.
2. Place it in the slot specified by the provider.
3. Save and publish.
4. Test on the custom domain, including mobile behavior.
5. Remove an unused or broken snippet, save, and publish again.

Do not paste private API keys into Custom code. Check consent behavior before adding analytics, advertising, or other tracking snippets.

Owners and Admins can add private values in Environment variables or the secure request card shown by Launch.

Enter a name and a value. The service request in the site's code determines where a value may be used. Saving a key alone does not create an integration.

1. Open Site overview → Environment variables, or the secure request card in the conversation.
2. Check the requested service and purpose.
3. Enter the exact variable name and its value.
4. Save the variable.
5. Ask Launch to complete the intended integration and test its result.

Keep secret values out of chat, site files, screenshots, and public snippets. The agent can work with the variable name without receiving the value.

A site's private keys are available only to permitted service requests. A new request created by an Editor can wait for an Owner or Admin to publish it.

Preview access to private service requests also requires the appropriate role. A permission refusal is not evidence that the key is wrong.

1. Have the Owner or an Admin review the service and intended request.
2. Publish the checked version with that role.
3. Test the live action using suitable test data.
4. Verify the destination record before relying on the integration.

A public visitor may repeat an action the website exposes. Keep business permissions and payment confirmation checks in the destination service.

Separate a missing value, a restricted site request, a provider refusal, and a snippet that runs only on the custom domain.

1. Read the visible error without copying the key value.
2. Confirm the variable name and service permissions.
3. Check that the intended version was published by an authorized role.
4. Test a custom-code snippet on the custom domain.
5. Use Help with the service name, page, action, and redacted error.