Connect the platforms Xenia reads from and sends through, one environment at a time.
A connector is a link to a system you already use. Connectors are what make Xenia useful: they bring your customer, order, and content data in, and they carry your messages out. Almost nothing else in the app works until you have at least one.
Open Connectors in the Operate section. Anyone can see what is connected. Adding, editing, and removing connectors is for Admins and Developers.
The page
Connectors are laid out in three parts:
Search filters all of it at once, which is faster than scrolling the catalog.
Connectors belong to one environment
A connector is set up for one workspace and one environment. An email provider added in your development environment does not exist in production, and a journey published to production will not send if the channel it needs was only set up elsewhere.
That separation is deliberate: it lets you point testing at a sandbox account and your live workspace at the real one without any risk of crossing them.
A journey that worked in one environment and quietly sends nothing in another is almost always missing that connector in the environment it was published to.
Adding a connector
Find the integration
Search or browse the catalog and choose the system you want to connect. Each one links out to the provider's own instructions for finding the credential it needs.
Connect it
Most connectors ask for an API key. Shopify, Meta, and HubSpot instead send you to the provider to sign in and approve access, then bring you back.
Save
Credentials are encrypted when saved and are never shown again. To change one, edit the connector and enter the new value.
Check its health
Connected connectors show whether they are healthy or erroring. Worth a glance before a launch rather than after.
What you can connect
Messaging channels
Platforms and APIs
More integrations are added over time, so the catalog in your workspace is the current list.
Setting up Resend
Resend is the quickest way to start sending email from your own domain, and the only connector that reports delivery results back to Xenia. Setup runs in two passes, because Xenia has to give you something before you can finish.
Create the API key
Sign up at Resend, add your sending domain, and add the DNS records it gives you at your domain registrar. Verification usually completes within minutes. Then create an API key and copy it.
Either permission level works. A Sending access key is the safer choice and is what Resend recommends. Xenia cannot read your domain list with one, so it will ask you to type the sender address instead of picking it from a list.
Save the connector
Paste the key into Xenia, press Verify, then set your sender address. If the key works but no domain is verified yet, Xenia tells you so rather than failing quietly. Save.
Your sender address must be on a domain you verified in Resend. If it is not, Resend refuses the send with "not authorized to send emails from that domain".
Register the webhook
Saving generates a webhook URL, shown in the connector with a copy button. In Resend, open Webhooks, add an endpoint with that URL, and subscribe to the delivered, bounced, complained, and failed events.
Paste the signing secret back
Resend shows a signing secret when you create the endpoint. Copy it into the connector's Webhook Signing Secret field and save again. Xenia rejects any webhook that is not signed with it.
Skip it and Xenia still sends, but it cannot see bounces. Repeatedly emailing addresses that no longer exist is one of the fastest ways to damage your sender reputation and end up in spam folders.
Your sender address has to be on a domain you verified in Resend. Sending as
you@gmail.com will not work, with Resend or any other provider.
What connecting unlocks
Connectors do more than store credentials. They decide what you can build:
- Shopify adds store and storefront triggers, plus steps that enrich a customer, check whether an order was placed, create a discount, and serve page variants.
- HubSpot adds a contact trigger, plus steps to update a contact, sync a list, and create a deal.
- Meta adds a lead form trigger, plus conversion and audience sync steps.
- Klaviyo, Contentful, Content Cloud, and GA4 / Warehouse add steps that fetch data mid-journey so later steps can branch on it.
- Resend reports delivery results back: you see which messages were delivered and which bounced, and addresses that hard-bounce or report spam are automatically stopped from receiving anything further.
Steps whose connector is not set up appear as unavailable, rather than letting you build something that would fail when it runs.
Connectors and audiences
The Audiences page needs customer data to work with. Shopify, Klaviyo, and HubSpot are the sources it reads, and the ready-made segment templates it offers are chosen based on which of those you have connected. Connect none and it will ask you to connect one first. See Audiences.
Keeping credentials safe
Credentials are encrypted and cannot be read back out of the app, by you or anyone else. For the connectors that sign in through the provider, access is kept current automatically, so you are not re-authorizing every few weeks.