Create a GitHub issue when a lead is created in Bitrix24

■Overview

Do you manually create GitHub Issues for development requests and inquiries from customers managed in Bitrix24? Although this process is straightforward, it can lead to human errors such as transcription mistakes and missed follow-ups. With this workflow, you can automate the integration between Bitrix24 and GitHub and automatically create GitHub Issues based on new lead information. This eliminates the time and errors associated with manual work, enabling faster and more accurate information sharing.

■Who This Template Is Recommended For

• Teams that manage development tasks in GitHub based on lead information from Bitrix24
• Teams looking to reduce the effort of manually transferring information and respond to customers more quickly
• Teams that want to automate the integration between Bitrix24 and GitHub and improve overall productivity

■Benefits of Using This Template

• When a lead is created in Bitrix24, a GitHub Issue is created automatically, reducing the time previously spent on manual work.
• With manual data entry eliminated, you can prevent human errors such as input mistakes and missed information sharing while maintaining data accuracy.

■Workflow Steps

1. First, connect Bitrix24 and GitHub to Yoom.
2. Next, select Bitrix24 as the trigger and set the “New Lead” action.
3. Finally, select GitHub as the operation and set the “Create Issue” action.

※ “Trigger”: An action that starts the flow. “Operation”: An action that processes data within the flow after the trigger starts.

■Customization Options

• When setting up the action to create a GitHub Issue, customize the Issue title, body, and other fields as needed.
• Include the lead title, details, and other information retrieved by the Bitrix24 trigger in the Issue so the development team can quickly access the information they need.

■Notes

• ‍‍Connect both Bitrix24 and GitHub to Yoom.
• You can choose a trigger interval of 5, 10, 15, 30, or 60 minutes.
• Please note that the shortest available trigger interval varies by plan.