Under the Hood

The stack if you want to know

Most clients do not need every implementation detail. If you are evaluating us technically or approving what connects to your infrastructure, this page explains how we choose and validate the architecture for each deployment.

The exact providers, models, and integrations depend on the approved scope.

Workflow Orchestration

n8n

STL Automate's internal production automation runs on self-hosted n8n, an open-source workflow automation platform that handles triggers, logic branching, API calls, and integrations.

We chose n8n because it gives us fine-grained control over every node in the workflow without abstracting away the logic. When something goes wrong, we can see exactly where and why, not just that something failed.

Client deployments may be customer-owned or STL-managed depending on scope. Credentials and workflows are separated according to the approved deployment architecture.

Trigger typesWebhooks, schedules, email (IMAP), HTTP
Execution modelEvent-driven, stateful with wait nodes
Error handlingPer-node routing with fallback logging
DeploymentSTL-managed or customer-owned, depending on scope
SeparationDefined by the approved deployment architecture
Voice Infrastructure

Programmable Voice

The Phone Receptionist uses programmable voice infrastructure selected for the needs of each deployment. Provider, conversation model, speech services, and routing are configured for the approved call flow.

Where supported, call events and metadata can route into n8n for approved classification, logging, notifications, and follow-up preparation.

Provider, model, and phone-routing choices are tested and validated for each implementation before production use.

Voice providerSelected per deployment
Conversation modelConfigurable
Speech servicesConfigurable
Call metadataAvailable where supported
Phone routingExisting number, forwarding, SIP, or provisioned number where supported
Lead Intelligence

Scoring & Routing

Scoring and routing begin with explicit business rules. Where useful, AI-assisted classification can help interpret unstructured inputs such as email bodies and call transcripts.

Criteria, thresholds, models, labels, and routing rules are defined per implementation. They are tested against the customer's actual use cases before they affect production behavior.

Knowledge sources are selected according to the workflow. Customer-approved systems remain authoritative where applicable, and generated drafts can be grounded in the business information approved for that use.

Scoring approachExplicit rules with optional AI-assisted classification
CriteriaDefined and approved per implementation
Knowledge sourcesSelected from approved business systems
ThresholdsConfigured and tested for the use case
RoutingBased on approved outcomes and exceptions
Integrations

Common integrations include

Gmail / IMAP

Inbound email parsing, outbound sending, reply detection

Google Sheets

Lead logging, knowledge base, CRM-lite for smaller clients

Google Calendar

Booking detection, availability checks

Calendly

Appointment booking link injection and booking confirmation

HubSpot CRM

Contact creation, deal logging, pipeline updates

Slack

Hot lead alerts, meeting notifications, internal ops

WhatsApp (Twilio)

Real-time SMS/WhatsApp alerts for time-sensitive leads

Twilio SMS

Outbound SMS sequences, opt-out handling

Hunter.io

Email discovery for outbound prospecting workflows

Security & Data

What happens to your data

We come from a cybersecurity background. Data handling isn't an afterthought. It's part of the architecture.

We minimize access to what each workflow needs. Customer systems remain authoritative systems of record where applicable, while other approved components may process the minimum data required for the configured workflow.

We use managed credential mechanisms where supported and scope access to the minimum permissions required for each integration.

Regulated-data and compliance requirements require a separate review. STL Automate does not represent an implementation as HIPAA, PCI, SOC 2, or otherwise compliant merely because particular software vendors are used.

Want to go deeper?

If you have architecture questions, integration edge cases, or security requirements, book a technical call. We'll go into as much detail as you need.

Book a Technical Call