IntegrationsServiceNow
ServiceNow implementations are mostly repeated configuration, rebuilt by hand per instance, promoted through update sets that drift from each other. It is the clearest example of work that looks bespoke and is not.
Your AI, MCP server or API
Their workspace and approved access
Their entitled capabilities and version
Validation, health and the next action
Available today
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
What a forward deployed engineer does by hand today.
A scoped application or an integration built directly in the instance, developed in a sub-production instance and promoted through update sets. Nothing about this is a single install step.
The person whose calendar decides your go-live date.
The ServiceNow platform team, and a change request through the customer's own ITSM process. Which is, with some irony, managed in ServiceNow.
Whose identity the product acts as, and where that grant lives.
OAuth 2.0 against the instance, or basic auth against an integration user, which is still common and still what security review objects to.
The repeatable half, turned into software.
The instance OAuth flow, write-only customer app-secret storage, per-environment tokens, and validation that reads a real record and checks a named field survived the ACLs. ServiceNow cannot tell us which instance a grant belongs to, so the instance and its OAuth app are configured before installation rather than guessed after somebody approves something.
The half that is theirs and should stay theirs.
The instance, an OAuth API endpoint registered inside it, its update set process, its change windows, and every piece of configuration somebody added in 2018.
How capabilities map onto what the platform will let you do.
Roles and ACLs. A capability needs a role that needs an ACL that may or may not exist in this instance.
What has to execute before anyone is told it works.
Health checks against the instance, and execution in a sub-production instance before production is touched.
Rotation, expiry, revocation, and who notices first.
Instance-scoped OAuth tokens, or an integration user whose password is in somebody's vault.
What happens to this customer when you ship version four.
Update sets are already a version mechanism and they drift. A per-customer deployment record that knows which update set is actually applied is the missing half.
What actually goes wrong, named rather than generalised.
Update set collisions. Configuration present in the sub-production instance and absent in production. Platform upgrades changing behaviour under a working integration.
How you learn it broke without the customer telling you.
Health reads the configured instance with the stored token and separates a revoked session from an unreachable ServiceNow dependency. Installation validation also reads a named field, because an ACL can return a row while hiding the data the capability needs.
Ready for customer deployments with customer-scoped authorization, validation and lifecycle management.
Available for customer deployments, with customer-scoped authorization, validation and lifecycle management.
Connect a source, approve what ships and send your customer an install link. 2 customer environments free. No card required.
