Last updated: 2021-06-07

Source: https://support.freshservice.com/support/solutions/articles/50000003578-sample-use-case-for-gitlab-orchestration-app-automate-gitlab-project-requests

Here’s a sample workflow to demonstrate the use of the Gitlab Orchestration app to automate the fulfilment of Gitlab Project Requests.

1. Create an event when a Service request is raised.

2. Followed by the condition to ensure the Service request is raised for Gitlab.

3. You can then pull in the App Node which will have the following configurations:

App Name: Gitlab - Orch

App Action: Look Up User By Email

Notes when Configuring Inputs:

  • email:   The value can be the user's primary email address. You can refer to it via the placeholder of the Requested for as shown below.

    • 4. To validate whether the user exists or not a condition node is added to check whether the status code is in between 200 - 300.

    5. If the user is found you can then pull in the App Node which will have the following configurations:

    App Name: Gitlab - Orch

    App Action: Look Up Project

    Notes when Configuring Inputs:

  • project\_name:   The value is the name of the Project for which the user needs to be added. You can refer to it via the placeholder of the Service request raised as shown below.

    • 6. To validate whether the Project exists or not a condition node is added to check whether the status code is in between 200 - 300.

    7. If the project is found you can then pull in the App Node which will have the following configurations:

    App Name: Gitlab - Orch

    App Action: Add User To Project

    Notes when Configuring Inputs:

  • project\_id:  The value is the Id of the Project for which the user needs to be added. You can refer to it via the placeholder of the previous action output as shown below.
  • user\_id: The value is the Id of the User who raised the request. You can refer to it via the placeholder of the previous action output as shown below.
  • access\_level: The value is as per the level of access needed. You can refer to it via the placeholder of the service request raised as shown below.

    • 8. To validate whether the User is added to a Project or not a condition node is added to check whether the status code is in between 200 - 300.

    9. If the workflow is successfully executed, add a note using the action node.