HttpRequest Automate

Automate interactions on Pipedrive with the HttpRequest Automate workflow, triggered manually to streamline pull request notifications. This integration efficiently checks for user existence by email and logs PR details, enhancing team collaboration and tracking.

7/8/2025
6 nodes
Medium
manualmediumpipedrivenoopgithubtriggerapiintegrationlogicconditional
Categories:
Manual TriggeredTechnical Infrastructure & DevOpsMedium WorkflowCRM & Sales
Integrations:
PipedriveNoOpGithubTrigger

Target Audience

This workflow is ideal for:
- Developers: Who manage pull requests in GitHub and want to track related contacts in Pipedrive.
- Sales Teams: Who need to follow up on pull requests that involve potential leads or existing clients.
- Project Managers: Who want to maintain communication with contributors and stakeholders involved in project development.
- Integrators: Who are looking to automate workflows between GitHub and Pipedrive for better productivity.

Problem Solved

This workflow addresses the challenge of tracking pull requests in GitHub and linking them to relevant contacts in Pipedrive. It automates the process of:
- Identifying the user who created a pull request.
- Searching for that user in Pipedrive by email.
- Creating notes in Pipedrive to document the pull request, ensuring that all team members are informed and can follow up effectively.

Workflow Steps

  • Trigger: The workflow is manually triggered when a pull request is created in GitHub.
    2. HTTP Request: It sends an HTTP request to retrieve the pull request details, including the sender's email and URL.
    3. Search in Pipedrive: The workflow searches for the user in Pipedrive using the email obtained from the pull request.
    4. Conditional Check: It checks if the person exists in Pipedrive by verifying if the name is not empty.
    5. Create Note: If the person exists, a note is created in Pipedrive to document the pull request.
    6. No Operation: If the person does not exist, the workflow performs a no-operation step, effectively ending the process.

    • Customization Guide

    To customize this workflow:
    - Change GitHub Repository: Modify the repository and owner fields in the 'ON Pull Request' node to match your GitHub account.
    - Pipedrive Fields: Adjust the fields in the 'Search PR user in Pipedrive by email' node to include additional data points relevant to your organization.
    - Note Content: Update the content of the note in the 'Pipedrive' node to include specific information that your team needs to track.
    - Add More Nodes: Integrate additional nodes for further actions, such as sending notifications or updating other systems based on the pull request status.