Summary
Who this is for
Admins set up and manage the connection between wxrks and Knak. You need connector administration access, and your account needs a plan that includes connectors. Admins and System Admins always have access; on other plans the Knak tile appears locked with an option to upgrade.
Knak users simply request translations from inside Knak as usual. They do not need a wxrks login for the request to be picked up.
If you do not see Integrations in the left sidebar, ask your account admin to grant connector access.
Key concepts
Term | What it means |
Knak | The enterprise email and landing-page builder where your marketing assets are created. |
Connector configuration | A saved connection between wxrks and your Knak account. You can have more than one. |
Translation request | A request created in Knak asking for an asset to be translated into one or more languages. This is what triggers wxrks. |
Webhook | The automatic notification Knak sends to wxrks the moment a translation is requested. |
Webhook URL and Webhook secret | The address and signing key you copy into Knak so it can notify wxrks securely. |
Org unit | The wxrks organizational unit that will own the translation projects created from Knak. |
Before you start
Have the following ready:
A Knak Enterprise account with API access, and permission to create an API token and add a webhook in Knak.
The wxrks org unit that should own the incoming translation projects. Make sure that org unit has a default source language and a default contact set, because wxrks uses them when a request does not specify them.
Connector administration access in wxrks (see "Who this is for").
Step 1: Open the Knak connector
In the left sidebar, select Integrations.
In the integrations gallery, find the Knak tile. You can use the search box or the Marketing & CMS filter to narrow the list.
Select Configure on the Knak tile.
If the Knak tile shows a padlock, your current plan does not include it. Use Upgrade Plan on the banner, or contact your account admin.
Step 2: Create the configuration
Selecting Configure opens the Add Configuration form with Knak already selected as the connector type.
Fill in the fields:
Field | What to enter |
Name | A label to recognize this configuration later (for example, your brand or workspace name). |
Org Unit | The wxrks org unit where translation projects should be created. |
Access token | Your Knak API key (Bearer token). Generate this in Knak and paste it here. It is stored securely and never shown again. |
The Webhook secret is generated for you automatically when you save, so there is nothing to enter for it.
Select Save to create the configuration.
Step 3: Connect wxrks to Knak
As soon as you save, wxrks shows a one-time confirmation panel with two values you must copy into Knak:
Webhook URL - the address Knak will send translation requests to.
Webhook secret - the signing key Knak uses so wxrks can trust the request.
Important: the Webhook secret is shown only once. Copy both values now. If you lose the secret, you can generate a new one later (see "Manage your configurations").
In Knak, open your webhook setup and:
Paste the Webhook URL as the destination.
Paste the Webhook secret as the signing secret.
Subscribe to the translation-requested event so Knak notifies wxrks whenever someone asks for a translation.
That completes the setup. From now on, translation requests flow automatically.
Step 4: How a translation flows
Start the request: In Knak, open the email or landing page you want to translate, go to the TRANSLATE tab, and click Request Translation.
Select the integration: From the list of available connections, select the wxrks configuration you previously set up.
Set the primary details: Review and select the Source Language of the asset being translated, then click Continue.
Choose target languages: Check one or more languages in which you want to receive the translation (for example, Portuguese) and click Next: Confirmation.
Confirm and submit: On the Your Translation Request Summary screen, review the details, set a Due Date, and add optional Notes for translation if needed. Then click Submit Request.
Track status: The request is sent and automatically creates a translation project in wxrks. In Knak's side panel, the translation status will change to Translation File Requested until the project is completed in wxrks and delivered back.You can watch and manage these projects from wxrks like any other project.
Manage your configurations
To review or change existing connections, go to Connectors from the sidebar. Each saved configuration is listed with its type and creation date.
From here you can:
Edit a configuration to update its name, org unit, or access token. Leave the access token blank to keep the current one.
Regenerate the webhook secret. The new secret is shown once, with a copy button, and a "Secret regenerated - copy it now" message. After regenerating, you must paste the new secret into Knak, or Knak's notifications will be rejected.
Delete a configuration you no longer need (a confirmation is required).
Good to know
Supported content: emails and landing pages requested from the Knak builder. You do not select an asset type in wxrks; wxrks translates whatever the Knak user requested.
One request per language: if a Knak user requests several target languages for the same asset, wxrks groups them into a single project for that asset.
Multiple accounts or brands: create a separate configuration for each Knak connection you need. Each has its own webhook URL and secret.
Secrets are write-once in the display: wxrks never shows a saved access token or webhook secret again. This is why the setup and regenerate panels highlight the values at the moment they are created.
Troubleshooting
Symptom | Likely cause and fix |
The Knak tile is locked in Integrations. | Your plan does not include Knak. Use Upgrade Plan, or ask an account admin. |
I can't find Integrations in the sidebar. | You lack connector access. Ask your account admin to grant it. |
A translation was requested in Knak but no project appears in wxrks. | Confirm in Knak that the webhook URL and secret are correct and that the translation-requested event is subscribed. Re-copy them from wxrks if unsure. |
Knak reports its webhook was rejected (unauthorized). | The webhook secret in Knak does not match wxrks. Regenerate the secret in wxrks (Connectors > Edit) and paste the new value into Knak. |
I lost the webhook secret. | Open the configuration under Connectors, select Edit, and Regenerate the secret. Copy the new value into Knak immediately. |
The project was created with the wrong source language. | wxrks uses the asset's language, then the org unit's default source language. Set a correct default source language on the org unit used by this configuration. |
A translation finished in wxrks but did not appear in Knak. | Delivery back to Knak is automatic. If it did not complete, check that the Knak access token is still valid (regenerate it in Knak and update it under Connectors > Edit). |
Quick reference
Task | Where |
Find and add the Knak connector | Sidebar > Integrations > Knak tile > Configure |
Enter Name, Org Unit, Access token | Add Configuration modal |
Copy the Webhook URL and secret | One-time panel shown right after saving |
Register the webhook | In Knak's webhook setup |
Edit, regenerate secret, or delete | Sidebar > Connectors |
Track translation projects | Your normal wxrks projects view |