Connect a custom integration
Register a customer-owned application, approve its product connection, and assign the credentials its workers need.
Register your service catalog, deployment system, or ticket application as a custom endpoint. Connect that identity to Infra or Guard through directional grants, then choose polling, signed events, or external record publication.
Before you begin
You need the following authority and application details:
- You have Connector Administrator authority in the organization.
- A native product administrator can approve the selected project or asset group.
- You know the application's HTTPS homepage, responsible team, and required resource and information scope.
Register the application
- In Console, open Organization → Connector → Integrations → Register integration.
- Enter the name, description, HTTPS homepage, and responsible team. Select Register integration.
- In the saved integration, record its integration ID. Confirm the owner and enabled state. Registration alone has no product-data grant.
For automation, use Register an integration.
Connect one product
- In Connector → Connections → Create connection, choose Infra or Guard for one endpoint and Custom integration for the other.
- Select the product organization and installation by ID. Select the registered integration ID for the custom endpoint.
- In Grants, choose the native source projects or asset groups and the custom integration as the destination. Select the required categories and label keys.
- To publish context back to the product, add the reverse direction with External context. Select the custom integration as source and the native project or group as destination.
- Review the selection. Have the native product administrator and Connector Administrator approve their endpoint participation, then select Overview → Activate connection.
- In Overview, confirm Connected, the active grant revision, and successful synchronization for the enabled directions.
If product approval is missing, the custom application's credentials cannot complete that approval. Inspect the pending endpoint in Grants.
Assign workers and prove the connection
- Follow Create Connector API credentials to bind a service account to this integration and connection. Select scopes for its task.
- For a catalog reader, complete Synchronize a service catalog and compare its first complete snapshot with the approved source scope.
- For an event receiver, complete Receive Connector events and confirm a signed test before enabling delivery.
- For context publication, complete Publish external context and confirm the record appears only on its explicitly mapped resource.
Use a separate connection for another native product. A registration can participate in several approved connections; a grant on one connection does not authorize exchange on another.