Connecting to webhooks from ProvisionPoint allow you to integrate with business systems, leverage third party workflow tools or apply additional business logic.

The details of a new request in ProvisionPoint can be sent to a webhook.  This is configured in the Developers tab of a Service Definition with two options, either a PRE or POST webhook.
All Webhook Urls will be created in tools outside of ProvisionPoint we will simply be the trigger with the request details.

 

The PRE webhook option sends the details of the request to the webhook as soon as the request is made and before the provisioning job begins.  There is also the option to pause the execution of the provisioning job until an external response is received. 
A PRE webhook is commonly used for logic outside of ProvisionPoint which will affect how the service is created, for example approval.

When using the PRE Webhook option ensure the message type of Detail is selected.  The message type of Summary is a legacy integration option.

The Information included in the PRE webhook can be seen here

The Body is an array of the following details

• webhookType
• actionTypeId: 1
• actionDetail (Array)
  • title
  • description
  • serviceDefinitionName
  • relativeUrl
  • parentUrl
  • classification
  • groupGuestAccess
  • externalSharing
  • visibility
  • privacySetting
  • requestForm (Array)
    • name
    • fields (array of any custom columns added via the request form)
      • name
      • columnId
      • columnTypeId
      • dateTimeValueFormat
      • valueString
      • valueBoolean
      • valueDateTime
      • valuesInt
      • valuePrincipal
      • valueTerm
  • requestedOwners
    • objectId
    • principalType
    • displayName
    • pictureUrl
    • upn
    • email
    • jobTitle
    • preferredDataLocation
    • disabled
    • proxyAddresses
    • isDefaultOwner
  • requestedMembers
    • objectId
    • principalType
    • displayName
    • pictureUrl
    • upn
    • email
    • jobTitle
    • preferredDataLocation
    • disabled
    • proxyAddresses
    • isDefaultOwner
  • import (true or false)
• operationId
• serviceInstanceId
• status
• error
• messageTime
• requestedBy
• aadTenantId
• appId
• value1 (status)
• value2 (operationId)
• value3 (ServiceInstanceId)

---

The POST webhook option sends the details of the request to the webhook once the provisioning job has completed successfully and the service has been created.   
A POST webhook is commonly used to update another business system with the details of a service that has been created or to apply additional configurations to the service which has been created.

When using the POST Webhook option ensure the message type of Detail is selected.  The message type of Summary is a legacy integration option.

The Information included in the POST webhook can be seen here

The Body is an array of the following details

• webhookType
• actionTypeId: 1
• actionDetail (Array)
  • title
  • description
  • serviceDefinitionName
  • relativeUrl
  • parentUrl
  • classification
  • groupGuestAccess
  • externalSharing
  • visibility
  • privacySetting
  • created
  • instanceCreated
  • leaseStartDate
  • leaseExpiryDate
  • formInstance (Array)
    • name
    • fields (array of any custom columns added via the request form)
      • name
      • columnId
      • columnTypeId
      • dateTimeValueFormat
      • valueString
      • valueBoolean
      • valueDateTime
      • valuesInt
      • valuePrincipal
      • valueTerm
  • serviceInstanceOwners
    • objectId
    • principalType
    • displayName
    • pictureUrl
    • upn
    • email
    • jobTitle
    • preferredDataLocation
    • disabled
    • proxyAddresses
    • isDefaultOwner
  • requestedMembers
    • objectId
    • principalType
    • displayName
    • pictureUrl
    • upn
    • email
    • jobTitle
    • preferredDataLocation
    • disabled
    • proxyAddresses
    • isDefaultOwner
  • import (true or false)
• operationId
• serviceInstanceId
• status
• error
• messageTime
• requestedBy
• aadTenantId
• appId
• value1 (status)
• value2 (operationId)
• value3 (ServiceInstanceId)

---

Webhooks can also be configured for any enabled Actions in the Service Definition, by selecting the Developer tab for the Action.

Ensure the Details option have been set in the Developer tab prior to adding the Action webhook Urls.

The Information will vary mainly on the ActionTypeId that will represent the action that has been run