Library / CRM & Sales Pipeline
CRM & Sales Pipeline
Match GitHub Pull Request Authors to Pipedrive Contacts
When a pull request is opened on GitHub, it looks up the author's email in Pipedrive and checks whether that person already exists.
What it does
# Httprequest Workflow ## Overview Automated workflow: Httprequest Workflow. This workflow processes data and performs automated tasks. ## Workflow Details - Total Nodes: 9 - Node Types: 7 - Error Handling: ✅ Implemented - Security: ✅ Hardened (no sensitive data) - Documentation: ✅ Complete ## Node Breakdown - HTTP Request: httpRequest - Search PR user in Pipedrive by email: pipedrive - person exists: if - Pipedrive: pipedrive - NoOp: noOp - ON Pull Request: githubTrigger - Error Handler: stopAndError - Workflow Documentation: stickyNote - Error Handler for 28409b8d: stopAndError ## Usage Instructions 1. Configure Credentials: Set up all required API keys and credentials 2. Update Variables: Replace any placeholder values with actual data 3. Test Workflow: Run in test mode to verify functionality 4. Deploy: Activate the workflow for production use ## Security Notes - All sensitive data has been removed or replaced with placeholders - Error handling is implemented for reliability - Follow security best practices when configuring credentials ## Troubleshooting - Check error logs if workflow fails - Verify all credentials are properly configured - Ensure all required services are accessible
The steps
- HTTP Request
- Search PR user in Pipedrive by email
- person exists
- Pipedrive
- NoOp
- ON Pull Request
- Error Handler
- Error Handler for 28409b8d
- Error Handler
- Error Handler
- Error Handler
- Error Handler
- Error Handler
- Error Handler
16 steps in total.
Similar automations
CRM & Sales PipelineAdd a Pipedrive Note When a GitHub Pull Request Is Opened6 stepsCRM & Sales PipelineCreate Pipedrive Leads from GitHub Repository Forks18 stepsChatbots & Messaging BotsDeadlock Match Stats Bot for Telegram7 stepsCode, Git & Developer ToolsBack Up n8n Workflows to GitHub via Pull Requests22 steps