Systems we have connected in production.

Verified 2026-09-28

OwnerRez integration

Routeless connects OwnerRez to custom booking and marketplace software through OAuth, property import, availability synchronization, and booking-block workflows. In Furnished Habitat, OwnerRez property and booking data is mapped into the marketplace while outbound blocks keep the external calendar aligned. The implementation records upstream errors instead of treating every successful HTTP request as a completed sync.

Review workflows and evidence →

Verified 2026-09-28

PriceLabs integration

Routeless integrates PriceLabs pricing data with custom vacation-rental software. Furnished Habitat maps marketplace listings to PriceLabs identifiers, stores daily rates and minimum stays, accepts signed connector callbacks, and falls back to a base listing rate when imported pricing becomes stale. The implementation separates the Customer API polling model from the native PMS connector model.

Review workflows and evidence →

Verified 2026-09-28

iGMS integration

Routeless connects iGMS vacation-rental data to custom marketplaces through OAuth, property and listing mapping, calendar synchronization, and booking writes. Furnished Habitat verifies webhook signatures before updating local availability, prevents duplicate event processing, and keeps the external reservation identifier on confirmed bookings. Scheduled reconciliation remains separate from event-driven updates.

Review workflows and evidence →

Verified 2026-09-28

Stripe integration

Routeless implements Stripe payment and billing workflows for custom SaaS products, marketplaces, and operational software. Verified work includes Checkout Sessions, subscriptions, Stripe Connect OAuth, signed webhooks, event deduplication, and reconciliation from Stripe's current object state. Payment details stay at Stripe's boundary while the application stores the identifiers and business state needed to recover.

Review workflows and evidence →

Verified 2026-09-28

OpenAI integration

Routeless integrates OpenAI models into customer-facing products and internal workflows where the application owns validation, cost controls, and fallback behavior. Verified systems use structured outputs, tool-backed search, streaming conversations, lead scoring, tutoring, and content analysis. Model output is treated as untrusted application input, not as a guaranteed fact or completed business action.

Review workflows and evidence →

Verified 2026-09-28

Anthropic Claude integration

Routeless Radar connects to Anthropic's Messages API and Claude web search to test how a brand appears in grounded answers. The integration sends market context when available, collects the answer and cited sources, records usage and timing, and separates provider errors from successful observations. The free scan uses OpenAI, Gemini, and Perplexity, not Claude.

Review workflows and evidence →

Verified 2026-09-28

Google Gemini integration

Routeless Radar calls the Gemini API with Google Search grounding to measure brand visibility in current, source-backed answers. It records the response, grounding sources, returned search queries when available, usage, timing, and failure state. For local checks, the requested market is written into the prompt because this integration does not send a separate provider location field.

Review workflows and evidence →

Verified 2026-09-28

Perplexity integration

Routeless Radar calls Perplexity's Sonar API for search-backed brand discovery checks. The integration can include the target market as user-location context, then records the answer, returned search results or citations, usage, timing, and failure state. Perplexity belongs to Radar's base provider coverage and is measured as its own source, not blended with another provider.

Review workflows and evidence →

Verified 2026-09-28

Twilio integration

Routeless uses Twilio for SMS and WhatsApp messaging inside lead, booking, and automation workflows. Verified systems send operator alerts, receive inbound messages, process delivery callbacks, and reject invalid webhook signatures. Message transport is only one part of the implementation; consent, destination validity, template requirements, and permanent delivery errors remain application responsibilities.

Review workflows and evidence →

Verified 2026-09-28

WhatsApp Business integration

Routeless has implemented WhatsApp Business messaging through Twilio rather than a direct Meta Cloud API client. Verified workflows deliver lead alerts and booked-call summaries, receive inbound WhatsApp messages, and classify template or service-window failures. The provider distinction matters because credentials, sender onboarding, webhook verification, and error behavior belong to the Twilio transport used in production.

Review workflows and evidence →

Verified 2026-09-28

Resend integration

Routeless integrates Resend for transactional email, authentication messages, customer confirmations, operator alerts, and automation delivery. Verified systems also receive signed Resend or Svix webhooks for inbound messages and delivery events. Email failure is kept separate from the business transaction so a captured lead, account, or payment is not lost because one notification provider is unavailable.

Review workflows and evidence →

Verified 2026-09-03

Google Search Console integration

Routeless uses the Google Search Console API to collect finalized search-performance windows, analyze queries and pages, inspect selected URLs, compare sitemaps with observed search data, and freeze permissioned measurements into case-study records. Reports keep Search Console clicks separate from leads and revenue because the API measures search visibility and traffic, not downstream commercial attribution.

Review workflows and evidence →

Verified 2026-09-28

Google Analytics 4 integration

Routeless connects GA4 reporting data to internal analysis and public case-study workflows. The verified implementation uses the Data API for channel, source, user, session, and event reports and the Admin API to discover accessible properties. It excludes partial months from comparisons and does not treat GA4 sessions as interchangeable with Search Console clicks.

Review workflows and evidence →

Verified 2026-09-28

Google Ads reporting integration

Routeless has implemented Google Ads conversion tagging and paid-media reporting pipelines, not a custom direct Google Ads API client or generative ad-creative system. Verified work includes Google Ads conversion configuration on Routeless landing pages and Funnel-delivered Google Ads data modeled in BigQuery and dbt. The page documents that boundary so reporting evidence is not misrepresented as campaign mutation.

Review workflows and evidence →

Verified 2026-09-28

Google Sheets integration

Routeless connects Google Sheets to websites and operational systems when a spreadsheet is the practical interface for staff. Asian Market Escondido reads a large POS-derived catalog and mapping tabs through the Sheets API for product search and guides. Separate Routeless product work uses read-write Sheets workflows for reviewed operational updates.

Review workflows and evidence →

Verified 2026-09-28

Google Forms integration

Routeless connected Buckeye Exteriors' custom estimate form to Google Forms so the public website could keep its own interface while sending structured lead responses to the client's existing form workflow. The verified connection maps contact and project fields on the server. It is a Google Forms response integration, not an implementation of the Google Forms API.

Review workflows and evidence →

Verified 2026-09-28

Calendly integration

Routeless connects Calendly to lead, booking, and notification workflows. Verified work ranges from tracked scheduling embeds to per-business OAuth connections and signed invitee webhooks. Lead identifiers can travel through supported UTM fields so the booking event returns to the correct record, while duplicate deliveries and reschedules are handled as events rather than assumed to be one update.

Review workflows and evidence →

Verified 2026-09-28

Amazon Web Services integration

Routeless uses AWS for client platforms that need managed application workloads, databases, object storage, content delivery, backups, and monitoring. For Furnished Habitat and VisaMind, that includes hosting application services, storing images or private documents, and supporting controlled file access. The exact services and controls depend on the product, data, traffic, and recovery requirements.

Review workflows and evidence →

Verified 2026-09-28

DataForSEO integration

Routeless Radar uses DataForSEO's live Google SERP APIs to collect structured AI Overview and AI Mode observations. It parses answer text and references, keeps each surface separate, and records a valid no-result when Google returns no AI answer. This is an official API workflow, not scraping or automating the consumer search interface.

Review workflows and evidence →