No-Code SaaS Automation Platform  ·  View 01 of 21  ·  Context and scope

System Context

Who uses the platform, which third-party products it reaches, and what two adjacent documents own instead.

Editable source SVG draw.io All views
Trust Workspace IdP SAML / OIDC Provider consent OAuth grant People Automation author Workspace admin Platform operator Third-party SaaS — not ours CRM, forms, ticketing trigger capable Sheets, storage, docs Chat and mail Billing and finance unsafe writes SaaS Automation Platform trigger to effect Adjacent, out of scope Own-service DAG orchestration Outbound webhook fan-out builds, repairs policy, approval runs the fleet both ways records messages invoices author sign-in delegated scopes SaaS Automation Platform — System Context External / third party Person or role synchronous two-way Bottom row is deliberately unconnected: adjacent documents in this practice own it. v 1.0 · owner Integration Platform Architecture · date 2026-10

Decisions

  • Providers are drawn as classes, not brands: the architecture turns on a provider's capabilities — can it push, does it honour an idempotency key — not on its logo.
  • Billing and finance is called out as an unsafe-write class because that single property changes the execution guarantee the platform can offer.
  • The workspace identity provider and the provider OAuth consent screen are both external: the platform authenticates authors and acts for them, but owns neither trust root.

Scope boundary

  • In: trigger ingestion, the automation definition, durable step execution, credential custody, quota governance, and failure legibility.
  • Out, and unconnected on purpose: DAG orchestration of our own services, outbound webhook fan-out to subscribers, and standalone request dedup — each an adjacent document in this practice.

Risks

  • The platform's reputation is made of other people's uptime; an author attributes a provider outage to us.
  • Holding delegated credentials for 2.5 M workspaces makes this platform a high-value target for reasons unrelated to its own data.
All views High-Level Architecture  ▶
Solution Architecture v1.0 · Amazon Web Services · Integration Platform Architecture · 2026-10 · 21 views01-system-context