Create a GitHub issue when a specific contact is created in Apollo

■Overview

Are you manually transferring customer information managed in the sales support tool “Apollo” to “GitHub,” which is used by your development team? Cross-department information sharing like this is not only time-consuming but can also lead to transcription errors and missed updates. With this workflow, whenever a specific contact is created in Apollo, an Issue is automatically created in GitHub. This streamlines the connection between Apollo and GitHub and eliminates the inefficiencies of manual work.

■Who Is This Template For?

• Developers who manage contact information from Apollo as tasks in GitHub
• Teams using Apollo and GitHub that want to strengthen collaboration between sales and development
• Team leaders who want to resolve issues such as missed follow-ups and delays caused by manual information sharing

■Benefits of This Template

• Automatically create a GitHub Issue whenever a contact is created in Apollo, reducing the time spent manually sharing information.
• Prevent human errors such as missed Issue creation and data entry mistakes, improving the accuracy of follow-ups.

■How the Workflow Works

1. Select Apollo as the trigger and set the action to “When a contact is created.”
2. Next, configure branching in the operation so that subsequent steps run only when specific conditions are met.
3. Finally, select GitHub as the operation and set the action to “Create an Issue.” An Issue will then be created automatically based on the contact information in Apollo.

■Customization Options

• Use contact information, such as labels and stages, as conditions for branching. For example, you can configure the workflow to create an Issue only when a specific type of contact is created.
• When creating an Issue in GitHub, you can flexibly configure the workflow by inserting the contact name or company name retrieved from Apollo as variables in the title or body, or by assigning a fixed value to the person in charge.

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

■Notes

• Connect both Apollo and GitHub with Yoom.
• You can select a trigger interval of 5, 10, 15, 30, or 60 minutes.
• Note that the shortest available trigger interval varies by plan.
• Branching is an operation available on the Mini plan and above. On the Free plan, operations configured in workflows that include branching will result in an error.
• Paid plans, including the Mini plan, offer a two-week free trial. During the free trial, you can use apps and features (operations) that are otherwise subject to plan restrictions.