Tour Agency App

Connect AI agents to Tour Agency App, a CRM and booking management platform for tour operators. The connector exposes a single Verify Connection action confirming credentials and the connected user, with business events delivered as outbound webhooks configured inside the product.

1 action API key available

Tour Agency App website ↗ Platform Documentation ↗ Capability data verified 2026-08-04

A scheduled itinerary run starts for a receptive agency

Agent runs Verify Connection against the configured API key

Agent reads the returned account identity, the user ID and the email

Agent confirms that identity is the agency account this flow is authorized to act for

Agent halts the run when the key is rejected or resolves to a different account

Agent posts the expected account and the returned account side by side

The operations owner decides whether the run continues or holds until the key is corrected

What This Integration Enables

Be clear about what this connector is. Tour Agency App is a CRM and booking management platform for receptive travel agencies in Latin America, covering reservations, payments, quotes, team scheduling and WhatsApp automation, and its public API surface is a single verification endpoint. This connector exposes exactly one action, Verify Connection, which validates the configured API key and returns the identity of the account it belongs to as a user ID and an email address. There are no booking reads, no client reads and no payment reads here, because the platform does not publish endpoints for them.

There is also no trigger. Tour Agency App delivers business events for clients, activities and payments as outbound webhooks that you configure inside the product under Configuración and API, and it documents no subscribe or unsubscribe endpoint, so those events are not fetched through this connector and this connector creates no FlowRunner trigger. That leaves one honest job, and it is a job worth doing well: a small connector that answers the question every larger flow assumes it already knows, which is whether the credential in front of it still points at the account you think it does. In a flow that reads an itinerary from one system, prices it in another and confirms it to a traveller, the cheapest place to find out that a key was rotated is the first step.

Without FlowRunner

Credentials assumed good A key is pasted into a flow once and never checked again

Failures surface downstream A rotated or wrong key shows up as a confusing error in the system being written to

Multi-account confusion Agencies running more than one Tour Agency App account cannot tell which key is in play

With FlowRunner

Credentials verified before the run Verify Connection resolves the key to a named account before anything downstream executes

Failures surface at the boundary A rejected key stops the run at the first step instead of halfway through an itinerary sync

Account identity made explicit The user ID and email behind the key are read and compared, not assumed

Use Case Scenarios

Preflight Check on an Itinerary Run

A nightly flow assembles tomorrow's departures across several systems. Before any of that work starts, the agent runs Verify Connection and compares the returned user ID against the one the flow was built for. A valid key returns the account and the run proceeds. A rejected key stops the run at step one, with the failure named, rather than producing a half completed sync that someone has to unpick in the morning.

Key Rotation Confirmation

An operations lead rotates the API key in Configuración and API and pastes the new value into the FlowRunner connection. The agent immediately runs Verify Connection and reports the account the new key resolves to. If the email and user ID match the previous key, the rotation is confirmed and the scheduled flows stay live. If they do not, the rotation is treated as a misconfiguration rather than a success, and nothing that depends on the connection is allowed to run.

Multi-Account Guard

An agency group runs separate Tour Agency App accounts for separate destinations, and the automations that surround them write bookings and messages into shared downstream systems. Before a flow writes anything on behalf of one of those accounts, the agent runs Verify Connection and confirms the key belongs to the destination account named in the run. When the identity does not match, the agent stops rather than continuing against whichever account the key actually opens.

Human-in-Loop Highlight

This connector has one action and it makes exactly one claim: the key you configured belongs to this account. The moment worth gating is the moment that claim comes back wrong. When Verify Connection returns a user ID or email that does not match the account the flow was built for, the agent does not decide for itself whether the difference is a harmless rotation or a key pointed at the wrong agency, because it cannot tell those apart and the consequences land outside Tour Agency App entirely, in the bookings and traveller messages the surrounding flow is about to produce. It halts the run and routes to the operations owner: "Verify Connection resolved to user ID 4812, [email protected]. This flow expects user ID 3907, [email protected]. The key was updated two hours ago. Continue against the returned account, hold the run, or replace the key?" A person answers. Until they do, the itinerary sync does not run against an account nobody chose.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via email

Human decides

Agent resumes with decision

Agent Capabilities

1 actions

Account

Verify Connection Verifies the configured API key against the Tour Agency App account and returns the identity of the account the key belongs to. Calls the public verification endpoint and responds with the account's user ID and email. Use this to confirm the connection is valid before running automations.

Frequently Asked Questions

What can FlowRunner do with Tour Agency App?

FlowRunner agents can run Verify Connection in Tour Agency App.

Does connecting Tour Agency App to FlowRunner require OAuth?

No. Tour Agency App connects to FlowRunner with an API key, no OAuth flow required.

Can Tour Agency App trigger a FlowRunner workflow automatically?

Tour Agency App doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Tour Agency App

$100 in credits. No card required. Connect in minutes.

Start Building Free Talk to us