Choosing Integration Communication Paths
Key Takeaways
A VA-based or SaaS connector is selected for its supported target data and operations.
Use a supported resource API for on-demand queries or operations and explicit result checking.
Fire-and-forget events notify external consumers. Response-required triggers take a compatible business response.
Distinguish a service desk ticket, a request intake path, and verified target fulfillment.
Start with who initiates and what must return
An integration may pull current data, ask an external application to perform work, notify a receiver of a platform event, or obtain an answer that changes a running process. Each requires a different interface. Define the initiator, the supported target and operation, and whether the receiving system must respond with a decision. Decide how you will detect a missing or delayed result. A transport acknowledgement alone says little about the business outcome.
| Customer requirement | Candidate path | Evidence to check |
|---|---|---|
| Read accounts or make a supported change in a private directory | Supported VA-based connector with reachable directory | Source connector, cluster and directory operation |
| Connect directly to an eligible cloud target through a supported connector | Appropriate SaaS connector or other documented connectivity option | The connector operation and target authentication or API result |
| Pull a current authorized inventory on a given schedule | Documented resource API, scopes and result pagination | Completed pages, record scope and consistent cutoff |
| Notify an external monitoring system that an aggregation reached a terminal result | Account Aggregation Completed event subscription | Trigger payload and completion status, then receiver's own record |
| Add a reviewer chosen by an external service after a request is submitted | Response-required Access Request Dynamic Approval | Supported response mode, on-time response with required identity data and actual routing |
| Create and track a fulfillment ticket for configured provisioning work | Supported service desk integration | Ticket creation, status and actual target effect |
Work a notification and reconciliation case
A team wants prompt alerts after HR account aggregations and an auditable daily completeness check. A supported Account Aggregation Completed event can notify the team's external integration. The event can occur after a completed, terminated, or failed aggregation. The receiver should read the outcome from the documented payload and independently track whether the alert or follow-up work completed. For HTTP subscriptions, provide an authorized receiving endpoint that SailPoint can reach, inspect configured authentication, and test the JSON payload and any filter. SailPoint also documents Amazon EventBridge as a subscription option where applicable. Choose the supported setup for the receiver and tenant.
The event-trigger guide describes fire-and-forget as one-way notification without event resend in that trigger contract. Design a periodic reconciliation if a missing notification would disrupt a compliance or operating requirement. Query a documented API or review task evidence to account for expected runs. Avoid building the entire audit record out of notifications alone. Reconciliation also helps separate an outbound notification delivery issue from an aggregation result. An on-demand API read can recover observed state or retrieve a supported record, without needing the event service to reproduce its notification.
Work an interactive approval case
A different team wants an external policy engine to choose an additional approver for a submitted request. Use the dynamic approval event if it is supported by the request setup. A response-required trigger supports a business response and has one subscriber per trigger. In a documented synchronous interaction, the subscriber must return the required successful response and payload within the allowed window. For the documented asynchronous mode, the receiver acknowledges the request under the configured response contract, and submits the actual business response later through the supported invocation completion path before the configured deadline. An acknowledgement without completion does not supply the approver. Test the payload, identity mapping, and resulting request route in the tenant. Save the subscription invocation record and the receiver’s own result for the same request. Neither alone proves that the approval process assigned the requested reviewer.
A workflow can also react to events and run ordered actions inside SailPoint. A service desk integration fits configured ticket-based provisioning interactions. A ServiceNow Service Catalog integration can let users initiate access from ServiceNow. Pick the direction and outcome required by the customer rather than treating the catalog and service-desk ticket path as interchangeable. A ticket record and a successfully updated native account are separate evidence. Use the operation results and the target evidence that match the required downstream effect.
See SailPoint’s source types, event types, available triggers, response modes, subscription and testing, and ServiceNow integration choices.
A dashboard uses Account Aggregation Completed notifications. What should it check before counting a run as successful?
The source status at the start of the calendar day.
Whether the webhook returned any network response.
The reported aggregation outcome for that run and the matching task evidence as needed.
Whether its OAuth client can list identities.
An external policy engine must nominate an approver in the running access request process. Which integration supplies the required decision?
A response-required dynamic approval trigger with the documented approver payload and response mode.
A fire-and-forget aggregation subscription.
An export of identities at a later scheduled time.
A target system connectivity test.
Sections you finish are checked off in the contents.