A connection can hide its contract
A green credential check does not explain which objects, fields, identifiers, history, or consent rules the workflow actually uses.
How integrations work
Connect tools, validate the data, and monitor every sync.
Vendo treats every connection as an explicit data contract. Check direction, fields, identity, permissions, schedule, history, and validation before a workflow becomes production-critical.
Explicit directionInspectable contractVisible run history
Connection contractInspectable by design
Source
Orders + customers
Destination
Profiles + events
Data contract
Direction
Source → Destination
Schedule
Hourly
Identity
User ID + email
History
24 months
Timezone
Australia/Sydney
Consent
Required
Last run · 4,281 recordsHealthy
Why reliability needs context
A working connection needs more than credentials.
A connection is useful when you can see what it sends, where it sends it, who owns it, and whether it is working.
Source and destination are different jobs
Importing data and delivering data require different permissions, schemas, schedules, limits, and validation.
Provider timing varies
History, latency, retries, retention, rate limits, and late-arriving records depend on the provider and account.
Similar fields are not equivalent
Orders, charges, purchases, customers, and conversions need explicit meaning and stable identifiers—not just matching names.
Before production use
Check the data before you rely on it.
The exact connector setup varies, but every reliable workflow needs the same four questions answered and tested.
01
Check status and direction
Confirm whether the connector is available, beta, managed, or planned and whether it works as a source, destination, or both.
02
Define the data contract
List the objects, fields, identifiers, currency, timezone, consent, owners, and downstream purpose.
03
Confirm access, timing, and history
Choose the permissions, schedule, history, and fields the provider supports.
04
Validate before relying on it
Test sample records, duplicates, late arrivals, rejected data, identity matches, totals, and destination responses.
Availability language
Check support before you plan the workflow.
Available
Ready for supported production workflows.
Managed source
Operated through Vendo’s managed source path; streams and downstream modeling depend on configuration.
Beta
Usable with a changing contract or behavior; validate carefully.
Managed setup
Scoped and implemented with the Vendo team.
Coming soon
Planned but not yet open for setup.
Unavailable
Listed for discovery only.
What each connector page shows
Source direction
The objects, events, and fields Vendo can import.
Destination direction
The mapped data Vendo can deliver to the receiving tool.
Provider-specific access
OAuth, API keys, service accounts, webhooks, IAM, and network requirements.
Provider-specific timing
Schedule, latency, retries, retained history, and rate-limit behavior.