Integrate Alegra with GitLab

GitLab is an open source platform that allows users to manage projects, cplaborate and store code. It was created by software developers who wanted a better way to cplaborate and to allow their companies to avoid the cost of legacy tops. As such, GitLab wants to enable every team to easily deploy and use a single application to keep track of all their projects, from planning and development through to production support.

Alegra is a customer relationship management (CRM. top that enables organizations to effectively engage with prospects, clients and other audiences. Alegra’s client-facing products help companies manage a full customer lifecycle, including acquisition, conversion, retention and loyalty.

Alegra is a customer relationship management (CRM. system designed for businesses looking to manage their customers’ profiles and workflow processes efficiently. It supports a variety of features, including case management, customer support, purchase order processing, cash flow management, cplaboration and project tracking.

GitLab is an open source platform that allows users to manage projects, cplaborate and store code. It was created by software developers who wanted a better way to cplaborate and to allow their companies to avoid the cost of legacy tops. As such, GitLab wants to enable every team to easily deploy and use a single application to keep track of all their projects, from planning and development through to production support.

Integration of Alegra and GitLab

To begin the integration process, first establish your requirements. For this example we will be using Alegra as the CRM system and GitLab as the platform for managing projects and storing code. Before beginning any integration between Alegra and GitLab it is important to note that you will need:

Alegra Enterprise Edition or Alegra Professional Edition with an active subscription license. This integration requires Alegra Professional edition as only those versions have the ability to export data in JSON format. The free version of Alegra cannot provide this functionality as it does not contain the required function modules.You will need a GitLab account for your integration as well as access to the forums or blogs that contain information about how to make the connection between Alegra and Gitlab. You will need a GitHub account if you want to push your commits directly to your GitHub repository rather than having them sent to you via email or FTP. You will also need a cURL library installed on your computer.

From there, you can begin by creating an account on both platforms; however, because we are connecting Alegra and GitLab we will only be working with Alegra for this example. Once you have created your GitLab account you can log into the server and click on Applications > Add Application where you will find the Create button. You will then be provided with an application form where you can provide some basic information about your application, including its name, description, repository type, default branch, triggers/hooks, webhooks URL and access scopes. Once you have filled out this information click on the Create button at the bottom of the form. You will then be taken to your application’s page so you can complete some additional steps before connecting Gitlab with Alegra. First you will need to Copy your API Token which can be found in your app settings page under the “Access Tokens” tab. Now return to your application page within GitLab by clicking on Applications > Manage Applications > Your-Application-Name > Settings. You will then need to click on WebHooks under Hooks & Triggers which will take you to the WebHooks page where you can paste your API token. Below that click on Add WebHook Integration which will take you to another page where you can select which events you would like Gitlab to send emails about. From here you can choose whether or not you want commit notifications, push notifications or issues notifications sent by email. After selecting your desired options you can then enter your email address where you would like notifications sent as well as an optional name for each notification type (commit, push or issue. Finally hit Save Changes at the bottom of the page. Now return back to your application page by clicking on Applications > Manage Applications > Your-Application-Name > Settings again. On this page click on Integrations > Your-Integration-Name which will take you to another page where you can now select which events you would like received by Alegra. From here you can choose whether or not you want commit notifications, push notifications or issues notifications sent via Alegra chat message or email. After selecting your desired options you can then specify which chat room or email address within Alegra should receive these notifications along with an optional name for each notification type (commit, push or issue. Finally hit Save Changes at the bottom of the page. Now that both applications are connected you will need to create two applications within Alegra that use one of these new integrations; however, before doing so it is important to make sure that the GITLAB_API_TOKEN variable has been set within Alegra (see below for more information. If it has not been set up yet then go ahead and navigate back to your application page within GitLab by clicking on Applications > Manage Applications > Your-Application-Name > Settings again. On this page click on Integrations > Your-Integration-Name where you should see a “Use this integration” checkbox beneath the “Integration Type” section labeled “Activate Integration” . In order for this integration to run properly it must be activated by checking this box before attempting to start this integration within Alegra. Once it has been activated click on Details which will take you back to the application page where you should now see a list of supported integrations including Webhooks which indicates that this integration has been activated successfully . If it has been activated correctly then go ahead and return back to Alegra where we will now create our new integrations using the Webhook trigger/hook . Navigate back to Administration > Users & Permissions > User Accounts where you should see a drop down menu labeled “Type” . In this drop down menu select “External Application” from the list of available types . Then enter a name for the new application where it asks for “Application Name” . Next select a trigger/hook from the list labeled “Trigger/Hook Type” . We chose Webhook since we are using a webhook integration; however, if you chose Push or Issue when setting up your application in Gitlab then you would want to use Push or Issue instead when creating this application in Alegra . Now add an optional description for this new application before hitting Save Changes at the bottom of the screen . Once you do this you should then see a new entry for this application in the “Applications” section labeled “(Application Name)” containing information about how many times this application was triggered and what its status is . Now that we have successfully created this integration we can go ahead and create our second application in Alegra which uses our other Gitlab connection . Navigate back to Administration > Users & Permissions > User Accounts where you should again see a drop down menu labeled “Type” . In this drop down menu select “External Application” from the list of available types . Then enter a name for the new application where it asks for “Application Name” . Next select a trigger/hook from the list labeled “Trigger/Hook Type” . We chose Webhook since we are using a webhook integration; however, if you chose Push or Issue when setting up your application in Gitlab then you would want to use Push or Issue instead when creating this application in Alegra . Now add an optional description for this new application before hitting Save Changes at the bottom of the screen . Once you do this you should then see a new entry for this application in the “Applications” section labeled “(Application Name)” containing information about how many times this application was triggered and what its status is . Now that both applications have been created within Alegra we need to specify which one of our newly created integrations should handle each event coming from our connected Gitlab server . Navigate back to Administration > Users & Permissions > User Accounts where you should again see a drop down menu labeled “Type” . In this drop down menu select “External Application” from the list of available types . Then select either your commit notification ,push notification or issue

The process to integrate Alegra and GitLab may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.