The Guesty integration verifies the guest of each confirmed reservation in your Guesty account automatically. You connect once, choose the workflow the verification runs and the verification timing, and each confirmed reservation starts a verification for the guest when its verification opens (by default, as soon as it is confirmed), without any manual step. The guest’s verification link is written straight onto the reservation as soon as it qualifies, and the verification’s status is mirrored there as it progresses, so your team sees it where they already work.
This page covers the Guesty integration specifically. For the full list of available integrations and how connections work in general, see the Integrations overview.
When to use
Section titled “When to use”Connect Guesty when you want reservations to trigger identity verification on their own, instead of adding each guest by hand or through the API. It suits teams that:
- Take reservations in Guesty and want every confirmed guest verified before arrival.
- Want the verification link and its live status visible on the reservation record, so reviewers and front-desk staff do not switch tools.
- Want to control which reservations get verified (for example, skip a particular channel or status, or run it on a different workflow) with routing rules rather than code.
If you only verify guests occasionally, or you drive verification from your own system, the API or a bulk CSV import may fit better. You can use the integration alongside either.
How it works
Section titled “How it works”Once connected, the integration runs on its own:
- A reservation event arrives. Guesty sends a webhook to a private, per-connection address whenever a reservation is created or updated, including when it is canceled.
- The reservation status decides the action. The integration reads the reservation and acts on its status (see the table below). A confirmed reservation gets its verification link and starts a verification when its verification opens; a pre-commitment or pre-payment reservation is skipped; a canceled reservation withdraws a verification still waiting on the guest or on your account’s funds, and one already being checked or decided keeps its result.
- A verification is started. For a reservation that should be verified, the integration starts a verification bound to the default workflow you chose when connecting, or to the workflow a routing rule selects for it. It starts when the reservation’s verification opens. Before then, the guest’s link shows when they can start. The guest’s name, and their email and phone when present, are carried onto the applicant so reviewers can identify them in the console. The reservation’s confirmation code is stored as the applicant’s external reference.
- The guest is invited, if the invite is on. A new connection, including one you connect again after a disconnect, starts with Send the verification invite off. Turn it on to have the platform email the guest their verification link; leave it off if you would rather send the link yourself from Guesty using the link field described below. A connection that already exists keeps its setting, which the connection’s Edit drawer shows.
- The link and status are written back. The verification link is written onto the reservation as soon as the reservation qualifies, before any verification starts, and the status field shows Not yet open or Not started until a verification starts. An internal review link is written when the verification starts. The status field is then kept in step with the verification as it moves through review to a final outcome.
What each reservation status does
Section titled “What each reservation status does”The integration decides what to do from the reservation’s status. This is the default behavior for a new connection:
| Reservation status | What happens |
|---|---|
confirmed |
Gets its verification link, and starts a verification for the guest when its verification opens. |
inquiry, reserved |
Skipped by default. These are held or pre-commitment bookings, not a committed stay. |
awaiting_payment |
Skipped by default. The guest is verified once the booking is confirmed, not before payment clears. |
canceled, closed, declined, expired |
Treated as canceled. A verification still waiting on the guest, or on your account’s funds, is withdrawn; one already being checked or decided keeps its result. |
| Any other status | Skipped. An unrecognized status never starts a verification by mistake. |
A rule can have more than one condition, and it matches a reservation only when all of them match. For example, a rule can have two conditions: Location ID is one of L-100, and Source is not one of Example Channel. That rule matches each reservation at listing L-100 whose Source is not empty and is not Example Channel, in any capitalization. A reservation whose Source is empty does not match it. To include those reservations, use is not one of, or empty. The Integrations overview describes each operator.
A rule can also use Lead time (days), the number of whole days from the day a reservation was made to its arrival date:
- Lead time (days) is worked out from two dates, on the listing’s calendar. Guesty records the time a reservation was made in UTC, and the integration places that time on the calendar of the listing’s time zone. So a reservation made at 9:30 PM listing time, on the evening before its arrival date, has a lead time of
1, not0.0is the same day. A reservation made after its arrival date has a negative lead time. The arrival date is the listing’s own check-in date as Guesty records it, or, when Guesty does not send that date, the day of the check-in time on the listing’s calendar. The rule builder also offers is less than, is at most, is greater than, and is at least for this field. The Integrations overview describes them. - How a lead time is compared. As a whole number of days, so +03 matches 3.
- Lead time needs the listing’s time zone. A Guesty reservation does not carry its listing’s time zone, so the integration reads it from the listing in Guesty, only when a rule needs the lead time. A listing that has no time zone in Guesty gives no lead time.
- Lead time needs the time the reservation was made. A reservation event from Guesty may arrive without it. The integration reads it when it reads the reservation from Guesty again, which it does when the reservation’s verification opens later than the moment the reservation reaches Checktiv (see Verification timing). Until then, and for a reservation that is never read again, a reservation whose event did not include that time has no lead time.
- A reservation with no lead time matches no condition on it. Whatever the operator, no condition on Lead time (days) matches such a reservation. So a Skip verification rule on this field never skips it. A rule on another field, such as Source, still applies to it.
Only the verification link, the review link, and the verification status are ever written back to Guesty. No applicant personal data is sent to Guesty.
Routing rules on guest details
Section titled “Routing rules on guest details”First name, Last name, Full name, Email, and Phone come from the guest’s details in Guesty. The integration reads those details before it evaluates a rule with a condition on one of these fields.
When Checktiv has the guest’s details, an empty guest field matches only is not one of, or empty. On Phone, a value with no digits, such as n/a, counts as empty. Phone reads only the digits 0 to 9, so a number in other digits, such as Arabic-Indic digits, also counts as empty.
A guest is unknown when the integration finds no guest details, or when the name, email, and phone of the guest are all empty.
A rule whose only condition uses is one of on a guest field does not match the reservation of an unknown guest. Checktiv then evaluates the next rule against the reservation. A Skip verification rule below can then skip the reservation.
Every other rule with a condition on a guest field is different. This covers any such rule with more than one condition. It also covers any rule that uses is not one of or is not one of, or empty on a guest field. For these rules, an unknown guest does not cause a skip. A Skip verification rule like that does not skip the reservation. A Select workflow rule like that can make Checktiv ignore the rules below it. This happens when the rule has no condition outside the guest fields, or when its conditions outside the guest fields match. The reservation then runs on the default workflow.
A phone with no digits counts as empty. If the guest’s only detail is a phone such as n/a, the guest is unknown, and the rules above apply.
Connecting Guesty
Section titled “Connecting Guesty”You need the Owner or Admin role, an active organization, and at least one workflow template to bind the connection to. Create a workflow first if you do not have one; the connect form links you to the workflow editor when none exist.
You connect using one credential: an integration token you generate from your Guesty account.
-
In your Guesty account, open the Marketplace, connect this integration, and generate an integration token. Generate it right before you connect: the token is single-use and expires a few hours after you create it (about four hours).
-
In the console, open Integrations and choose Guesty.
-
Paste the integration token. Do this promptly and finish the form without much delay, because the token is single-use and short-lived.
-
Choose the default workflow the integration runs for each reservation. This is required. Every verification the connection creates uses this workflow unless a routing rule skips the reservation or selects another workflow for it. The list shows your active workflows, with your organization default marked.
-
(Optional) Add routing rules to change which reservations are verified. The connection starts with a rule that skips
inquiryand awaiting-payment reservations. You can keep it, edit it, or remove it, and add rules of your own. Each rule has one or more conditions, and each condition compares a field (such as Source or Record status) with one or more values. When all of its conditions match, the rule either skips the reservation or selects the workflow it runs. -
(Optional) Turn on the Send the verification invite toggle to have the platform email each guest their verification link. It is off for a new connection. Leave it off if you plan to send the link yourself from Guesty using the written-back link field.
-
(Optional) Set the Verification timing. By default, verification opens when a reservation reaches Checktiv and is due at the first verification’s own deadline. To open it later or make it due at another time, see Verification timing.
-
Select Connect. The button stays disabled until a workflow is chosen and the token is filled.
On a successful connect, the platform exchanges the integration token for durable credentials, registers the reservation webhook in your Guesty account, and creates the custom fields it writes back into (see below). The connection then appears in your Integrations list.
Fields we set in Guesty
Section titled “Fields we set in Guesty”The integration provisions three custom fields on your Guesty reservations when you connect, and fills them automatically as verifications progress. All three are reservation-scoped text fields and are visible in Guesty.
| Field name | When it is set | What it holds |
|---|---|---|
verificationLink |
When the reservation qualifies | The reservation’s verification link for the guest. Share this with the guest if you send invites yourself. |
verificationReviewLink |
When the verification starts | An internal link your team uses to open the verification in the console. Not for the guest. |
verificationStatus |
When the reservation qualifies, then updated as it progresses | The verification’s current status for the reservation’s guest: Not yet open or Not started before a verification starts, then from in-progress through review to the final outcome, or Not completed by deadline. |
A few details worth knowing:
- The link written to
verificationLinkis the reservation’s own link, so it is on the reservation before any verification starts. It is safe to keep on the reservation, and opening it does not use it up the way a one-time link is used up. It stays the same for the whole verification window: before verification opens it shows the date it opens, while it is open it starts or continues the verification, and after the due time it says the deadline has passed. It changes when the reservation is canceled (the link stops working), restored in Guesty after a cancellation, or given a different guest. See Verification timing. - A guest who opens the link again after finishing sees where their verification stands (for example, submitted and under review) instead of an error. The link never reopens a finished verification. A guest whose earlier verification lapsed before any paid check can start again from the same link while verification is open.
- The status field tracks the verification live. It is set when the reservation qualifies and updated as the verification moves through its stages, so the reservation always reflects the current status, ending on the final outcome.
- These fields only ever carry the links and the status. They never carry the guest’s personal details.
- The written-back result lands on the exact reservation the verification came from, so a status cannot be recorded against the wrong booking.
Troubleshooting
Section titled “Troubleshooting”Connecting did not go through, or the token was not accepted. Guesty integration tokens are single-use and expire a few hours after you generate them. A token that was already submitted once, or that sat unused past its expiry, cannot be reused, even if the problem looked unrelated to the token itself. Go back to Guesty’s marketplace, generate a fresh integration token, and try connecting again.
The connection shows “Reconnect needed.” The stored credentials are no longer valid, usually because the connection was disconnected in Guesty or access was revoked. Open the integration, choose to reconnect, generate a fresh integration token in Guesty’s marketplace, and paste it in. Your workflow, routing rules, and invite setting carry over.
A reservation did not create a verification. Check, in order:
- The verification timing. A reservation whose verification has not opened yet already has its link, and its status field shows Not yet open. Its verification starts when verification opens. See Verification timing.
- The reservation status. Only
confirmedreservations are verified by default. Aninquiry,reserved, or awaiting-payment reservation is skipped until it is confirmed, and a canceled reservation is never verified. See the status table above. - Routing rules. A reservation that matches a Skip rule is intentionally not verified, and one that matches a Select workflow rule runs that rule’s workflow instead of the default. Review the connection’s rules, including the rule that skips
inquiryand awaiting-payment reservations, against the reservation’s fields (for example, its status or booking source). - The reservation event. The integration acts on reservation events from Guesty. A reservation created outside the connected account, or before the integration was connected, will not have triggered one.
- The workflow. The connection must be bound to an active workflow. A workflow an integration uses cannot be deactivated or deleted from the console or the API, but a connection set up before that protection can still point at an inactive default workflow. The connection’s form flags it; open the integration, choose Edit, and choose an active one. You can leave the credential fields blank.
The custom fields are missing in Guesty. The three fields are provisioned automatically when you connect. If they are absent, reconnect the integration to recreate them. Do not rename or remove them in Guesty, or the write-back cannot be delivered.
A guest did not receive their invite.
Confirm the Send the verification invite toggle is on for the connection. A new connection starts with it off, and while it is off the platform does not email the guest; you are expected to send the link yourself using the verificationLink field written onto the reservation. Turning it on invites each guest whose verification opens after the change. To invite a guest whose verification already started, open it in your Applicants list and select Send invite (see Resend or revoke). If their verification has not started yet, share the link in the verificationLink field written onto the reservation. Also confirm the reservation carried a guest email, since there is no address to send to otherwise. If that email address reached the per-recipient invite limit of three invite emails in an hour, the verification starts but Checktiv sends no invite. Open that verification in your Applicants list and select Send invite.
The status is not showing on the reservation.
The status field (verificationStatus) is written when the reservation qualifies and updated as it progresses. If a reservation qualified but the field is empty, confirm the custom field still exists in Guesty under its original name; reconnect the integration to recreate it if it was renamed or removed. If no verification started, check the reservation status and routing rules above first.
You want to stop the integration. Disconnecting the connection removes the reservation webhook in Guesty and stops all further write-backs. Verifications that already started continue, but the verification links on your reservations stop working. To start again later, reconnect with a fresh integration token; a reservation then gets a new link the next time it changes in Guesty.