Skip to content

feat(integrations): add support for Recruitee #3750

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

albertocubeddu
Copy link

Even replacing the SVG with an existing integration i was not able to see the image:
image

image
The integration seems to work, what is the best way to test it out from localhost? (e.g. calling the proxy?)

Thanks in advance.

Copy link
Contributor

@hassan254-prog hassan254-prog left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @albertocubeddu for your contribution, small comments inline but everything else looks great 🎸 , nice catch on adding the proxy.verification method.
Just curious is the api key scoped?

- ats
auth_mode: API_KEY
proxy:
base_url: https://api.recruitee.com/c/${connectionConfig.company_id}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

would be good to have company_id as camelCase.

method: GET
endpoints:
- /candidates
docs: https://docs.recruitee.com
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The docs page should link to the internal Nango documentation. Could you also include the Connect-UI documentation? You can follow this example: here. Would also be nice to include the pattern, example and docs_section for both credentials and connection_config

@hassan254-prog
Copy link
Contributor

@albertocubeddu , after adding a new image, you will need to rebuild your webapp.
One way to test if the API Key is correct, is by adding the proxy.verification method which you already have. This will send a proxy call to the endpoint specified with the apiKey you have supplied and incase the api key is incorrect, Nango will throw an incorrect credential error. The other way to test is by creating a custom integration which you can run against the connection and provider you just added. You can follow steps in here to achieve that.

@bodinsamuel bodinsamuel changed the title feat(integration) Recruitee feat(integration): add support for Recruitee Mar 24, 2025
@bodinsamuel bodinsamuel changed the title feat(integration): add support for Recruitee feat(integrations): add support for Recruitee Mar 24, 2025
Copy link
Contributor

This PR is stale because it has been open for 30 days with no activity.

@github-actions github-actions bot added the Stale label Apr 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants