Skip to content

feat(integrations): add support for PreciseFP #3975

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 3 commits into
base: master
Choose a base branch
from

Conversation

h55nick
Copy link

@h55nick h55nick commented Apr 29, 2025

This PR adds support for PreciseFP OAuth integration.

  • Added PreciseFP provider configuration in providers.yaml
  • Created documentation files
  • Added PreciseFP logo from their official website
  • Updated mint.json to include PreciseFP in the documentation
  • Added API documentation URL from the official Postman documentation
  • Added rate limit information from the API documentation
  • Updated tooling status to accurately reflect implemented features
  • Simplified documentation links

Summary by mrge

Added PreciseFP as a new OAuth integration, including provider configuration, documentation, and logo.

  • New Features
    • Added PreciseFP to providers.yaml with OAuth2 settings.
    • Created integration documentation and usage details.
    • Included PreciseFP logo and updated documentation links.

Copy link

@cubic-dev-ai cubic-dev-ai bot left a comment

Choose a reason for hiding this comment

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

mrge found 7 issues across 3 files. View them in mrge.io

@@ -697,6 +697,7 @@
"integrations/all/wakatime",
"integrations/all/wave-accounting",
"integrations/all/wealthbox",
"integrations/all/precisefp",
Copy link

Choose a reason for hiding this comment

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

Integration entry not in alphabetical order

token_url: https://app.precisefp.com/oauth/token
authorization_params:
response_type: code
scope: "*"
Copy link

Choose a reason for hiding this comment

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

Using wildcard scope "*" requests excessive permissions

Copy link
Author

Choose a reason for hiding this comment

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

This is specified in their documentation

method: GET
endpoints:
- /api/v3/user
docs: https://docs.nango.dev/integrations/all/precisefp
Copy link

Choose a reason for hiding this comment

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

No rate limit configuration specified for the API

| Security audit | ❓ | |


## Setup guide
Copy link

Choose a reason for hiding this comment

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

Setup guide section is empty despite PR description mentioning 'Added PreciseFP provider configuration in providers.yaml'

<Note>Contribute useful links by [editing this page](https://github.com/nangohq/nango/tree/master/docs-v2/integrations/all/precisefp.mdx)</Note>

## API gotchas
- To implement OAuth for your application, you must be issued API credentials first. Please reach out to PreciseFP to get your API credentials (Client ID and Client Secret).
Copy link

Choose a reason for hiding this comment

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

Missing contact information or process for obtaining API credentials

## API gotchas
- To implement OAuth for your application, you must be issued API credentials first. Please reach out to PreciseFP to get your API credentials (Client ID and Client Secret).
- Once you have your API credentials (Client ID and Client Secret), you are ready to start implementing the OAuth Authorization.
- The scope of access should always be "*".
Copy link

Choose a reason for hiding this comment

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

Wildcard scope requirement mentioned without security implications or explanation

| Pre-Requisites | Status | Comment|
| - | - | - |
| Paid dev account | ✅ | You need API credentials (Client ID and Client Secret) |
| Paid test account | ❓ | |
Copy link

Choose a reason for hiding this comment

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

Multiple fields in the access requirements table use '❓' without explanation, leaving users uncertain about requirements

@h55nick
Copy link
Author

h55nick commented Apr 29, 2025

Thank you for the feedback! I have addressed all the issues:

  1. Fixed the alphabetical order in mint.json
  2. Added rate limit configuration to the provider (60 requests per minute)
  3. Added a complete setup guide with contact information
  4. Clarified the access requirements table with proper values
  5. Explained the wildcard scope requirement - this is specifically required by PreciseFP as their only accepted scope value

@h55nick
Copy link
Author

h55nick commented Apr 29, 2025

Regarding the wildcard scope "*": This is specifically required by PreciseFP as their only accepted scope value. I have added an explanation in the API gotchas section to clarify this requirement.

@h55nick
Copy link
Author

h55nick commented Apr 29, 2025

I have added rate limit configuration to the provider with 60 requests per minute as specified in the PreciseFP API documentation.

@h55nick
Copy link
Author

h55nick commented Apr 29, 2025

I have added a complete setup guide with detailed steps for obtaining API credentials and configuring OAuth in Nango.

@h55nick
Copy link
Author

h55nick commented Apr 29, 2025

I have updated the access requirements table with proper values (✅/❌) and added explanations where needed.

Copy link
Collaborator

@bodinsamuel bodinsamuel left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution, just a couple of small comments 👌🏻

Copy link
Collaborator

Choose a reason for hiding this comment

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

the svg seems invalid

Comment on lines +10020 to +10022
rate_limit:
rate: 60
period: 60
Copy link
Collaborator

Choose a reason for hiding this comment

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

This rate limit configuration doesn't exist on our side

Suggested change
rate_limit:
rate: 60
period: 60

@h55nick
Copy link
Author

h55nick commented Apr 30, 2025

I have fixed the logo issue by replacing the invalid PNG file (with SVG extension) with a proper SVG file that uses the PreciseFP brand colors.

@TBonnin TBonnin force-pushed the master branch 3 times, most recently from f519537 to 87a5092 Compare May 27, 2025 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants