Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Greptile OverviewGreptile SummaryThis PR adds comprehensive integration with Enrich.so, a B2B data enrichment and LinkedIn intelligence platform. The implementation includes 30 tools covering person/company enrichment, email finding/verification, LinkedIn data extraction, and post analytics. Key additions:
Implementation quality:
Confidence Score: 5/5
Important Files Changed
Sequence DiagramsequenceDiagram
participant User
participant Block as Enrich Block
participant Registry as Tool Registry
participant Tool as Enrich Tool
participant API as Enrich.so API
User->>Block: Configure operation & API key
Block->>Block: Validate & parse parameters
Note over Block: Parse JSON fields<br/>(currentJobTitles, skills, etc.)
Block->>Block: Map operation to tool name
Block->>Registry: Lookup tool by ID
Registry->>Tool: Return tool instance
Tool->>Tool: Build request URL/body
Note over Tool: Add Authorization header<br/>Bearer {apiKey}
Tool->>API: HTTP GET/POST request
API-->>Tool: JSON response
Tool->>Tool: Transform response
Note over Tool: Map API fields to output schema<br/>Handle queued responses (202)
Tool-->>Block: Return ToolResponse
Block-->>User: Output data
|
![greptile-apps[bot]](https://avatars.githubusercontent.com/in/867647?s=60&v=4){kind=small}
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| request: { | ||
| url: (params) => { | ||
| const url = new URL('https://api.enrich.so/v2/api/linkedin-to-email') | ||
| url.searchParams.append('linkedin_profile', params.linkedinProfile.trim()) |
There was a problem hiding this comment.
Both LinkedIn email tools use identical API endpoint
High Severity
The linkedInToWorkEmailTool and linkedInToPersonalEmailTool both call the exact same endpoint (https://api.enrich.so/v2/api/linkedin-to-email) with identical parameters. The Enrich.so API documentation shows separate endpoints exist for "Profile URL to Work Email" and "Profile URL to Personal Email". As currently implemented, users selecting the "LinkedIn to Personal Email" operation will actually get work email results (or the same results as work email), making the personal email feature non-functional.
Additional Locations (1)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Type of Change
Testing
Tested manually
Checklist