Integrations

The Integrations page in the dashboard header does two jobs: it connects WeTravel so a departure can pull its own traveler list, and it makes API keys so your own software can talk to Cordelle. Neither is required — a CSV paste still works, and most agencies never need a key.

WeTravel

If you take bookings on WeTravel, Cordelle can read each trip's participants and put them on the matching departure, so nobody retypes names out of confirmation emails.

Connect it once

In WeTravel, go to Business Settings → Branding & Pro Settings → Partner API Integration, and click Generate API Key.
In Cordelle, open Integrations and paste the key under WeTravel.
Press Connect. Cordelle checks the key against WeTravel before saving it, so you find out immediately if something was mistyped — not weeks later.

The key is stored encrypted. If you ever want it gone, Disconnect removes it; the trips you already linked stay linked and wake up if you reconnect.

Pull a roster

Open the departure and go to its Travelers tab.
Under Pull from WeTravel, choose the WeTravel trip this departure is, and press Link this trip.
Press Pull travelers now. You can press it again whenever bookings come in — running it twice never creates the same person twice.

What a pull will and won't do. It only ever adds people or fills in boxes that were empty. Nothing you typed in Cordelle is overwritten — if you corrected a spelling or added a mobility note, it stays exactly as you left it.

When someone in WeTravel matches somebody already on your roster, Cordelle joins them up rather than duplicating — by email address, or by an exact name match when the person you typed has no email. If two people on the list could plausibly be the same traveler, it does not guess: it leaves them alone and tells you to look, because a duplicated traveler on a departure is worse than a minute of checking.

Cancelled bookings are skipped. Every pull ends with a plain sentence saying how many people were added, how many already had details filled in, and anything it wants you to check by hand.

What WeTravel doesn't send

WeTravel shares participant names and email addresses. It does not share phone numbers, dietary requirements, mobility needs or emergency contacts — so those columns stay yours to fill in, by hand or by CSV. That matters most for the emergency contact, which is the one field you least want to discover is empty.

Zapier

Zapier connects Cordelle to the thousands of other tools it supports, without anybody writing code. Two things are wired up today:

New Traveler (a trigger) — fires when somebody is added to a departure's roster, so you can copy them into a spreadsheet, your mailing list, or whatever your office already runs on.
Add Traveler to Departure (an action) — puts a person on a departure's roster from anywhere else. A form on your website, a booking tool, a spreadsheet row.

It's in early access. Cordelle isn't in Zapier's public app directory yet — that needs a handful of operators using it first, which is a chicken-and-egg we're at the start of. Until then it works exactly the same, you just need the invite link below rather than searching for it in Zapier.

Getting set up

Open the invite link: accept the Cordelle integration (you'll sign in to Zapier first if you aren't already).
In Cordelle, open Integrations and make a key named “Zapier”. Copy it — it's shown once.
Build a Zap. When it asks to connect Cordelle, paste the key. It should come straight back with your agency name, which is how you know it worked.

Adding a traveler through Zapier is safe to run twice. If you fill in the External Reference field with your own id for that person, a repeat gets you the traveler who's already there rather than a second copy of them — which matters, because automations retry.

API keys

A key lets other software — your own scripts, or an automation tool — list your departures and add travelers to them. Open Integrations, give the key a name that says where it will live (“Zapier”, “booking site”), and press Make a key.

Copy it there and then. The key is shown once and never again — Cordelle keeps only a fingerprint of it, so we genuinely cannot read it back to you. If it's lost, revoke it and make another; that takes ten seconds.

A key is deliberately narrow. It can list departures, read a roster, and add a traveler. It cannot see your billing, change your team, turn off two-step sign-in, or make more keys. That is why handing one to another piece of software is a small decision rather than a large one. Revoke shuts it off immediately, and anything using it stops working straight away — so revoke the key for a tool you've stopped using, not the one your roster still flows through.

The list shows when each key was last used, which is usually how you tell which one is safe to retire.

None of this is required

Plenty of agencies run every trip without touching this page — no WeTravel, no Zapier, no keys. Typing a roster in, or pasting a CSV under Travelers, remains a first-class way to work — and if you'd rather start a whole departure from a document you already have, see Tours and departures.