…sed on changes in NangoHQ/integration-templates@cd7fcfb by Khaliq. Commit message: fix(lever-ashby) yaml cleanup (#131)

…sed on changes in NangoHQ/integration-templates@ef8abf3 by Daniel Roy Lwetabe. Commit message: feat(pennylane): Make penny lane syncs and actions into public templates (#127)

<!-- Describe the problem and your solution --> 
Update `salesforce-experience-cloud` to also have an `automated: true`
property

<!-- Issue ticket number and link (if applicable) -->

<!-- Testing instructions (skip if just adding/editing providers) -->

…3103)

<!-- Describe the problem and your solution --> 
When viewing a connection we had a strange state that was possible where
there was an auth error on a connection but because it was not a
connection that could be refreshed it wasn't showing the error in the UI
once viewing the settings.

<!-- Issue ticket number and link (if applicable) -->
See
https://linear.app/nango/issue/NAN-2255/authorization-tab-for-connections-sometimes-doesnt-show-auth-errors


<!-- Testing instructions (skip if just adding/editing providers) -->
## How I tested it

I set up an auth error row in my test db on a connection that didn't
refresh (I used Unauthenticated) and confirmed that it displayed
correctly. Here's a sample insert (you'll need to tweak it to get it to
work with a connection you have set up):

```
INSERT INTO "nango"."_nango_active_logs"("id","type","action","connection_id","log_id","active","sync_id","created_at","updated_at")
VALUES
(391,E'auth',E'token_refresh',73,E'begpVdnwQLenQDHNVicf',TRUE,NULL,E'2024-11-26 16:53:33.628375+00',E'2024-11-26 16:53:33.628375+00');
```

Before this change you would see the auth error in the connections list,
but visiting the connection would not show a dot on the auth tab or show
an error on that page. After this change you'll see the dot and the
error.

<!-- Describe the problem and your solution --> 
Refactored the response handling to cover more edge cases. Instead of
checking if the `content-disposition` header is exactly equal to
`attachment`, we now check if it includes `attachment` or `inline`,
allowing for more flexibility. This change improves the handling of
different content types by considering both attachment and inline
dispositions.
<!-- Issue ticket number and link (if applicable) -->

<!-- Testing instructions (skip if just adding/editing providers) -->
Initially this was producing a malformed response with the dropbox and
front providers, but after the fix, it works as expected.

---------

Co-authored-by: Hassan Wari <[email protected]>
Co-authored-by: Khaliq <[email protected]>

…sed on changes in NangoHQ/integration-templates@fe1184f by Khaliq. Commit message: fix(lever): more cleanup of endpoints (#134)

…sed on changes in NangoHQ/integration-templates@06bf127 by Khaliq. Commit message: feat(avalara): Add avalara syncs and actions (#133)

…sed on changes in NangoHQ/integration-templates@5f28b04 by Hassan_Wari. Commit message: fix(front): add cursor in request param for pagination (#135)

## Changes

Fixes
https://linear.app/nango/issue/NAN-2304/connect-support-oauth-scopes

- Support passing `oauth_scopes_override`  and `user_scopes`


## Tests

I don't know, if you have an idea of an integration that supports this
let me know :D

## 😘 Changes

Fixes https://linear.app/nango/issue/NAN-2188/test-connection-ui

- UI: New create connection page
~The goal is to give the opportunity for customers to change the
`EndUser` (also education time) and display links to documentation. It's
one more click but yeah.~

- UI: Keep the legacy page to a new endpoint for a moment
- UI: add new style for Button, Input, Select
https://www.figma.com/design/pMnSC7rhSM79Dqwhm7MFhd

- `POST /api/v1/connect/sessions` now accepts the same payload as the
public one
- `GET /api/v1/meta` expose user UUID 
~Not sure what the use of id but it's handy to have static-random id for
the endUser profile without exposing our auto-incremented number.~
unused in the end

## 🧪 Tests

- Go to UI > Connections > Create
- Also go to Integrations > any > Add connection

![Screenshot 2024-12-02 at 13 17
52](https://github.com/user-attachments/assets/c2f9b096-1ecc-4deb-ad44-69fca96af931)

## Changes

Improve validation for providers
- Detect invalid path
- Detect missing doc_connect
- Detect invalid doc_section

This reverts commit 3dd1ebb.

<!-- Describe the problem and your solution --> 
Add rate limiting to both the documentation and the `providers.yaml`. 
<!-- Issue ticket number and link (if applicable) -->

<!-- Testing instructions (skip if just adding/editing providers) -->

---------

Co-authored-by: Hassan Wari <[email protected]>

## Changes

This provider is doomed, greenhouse has 7 different APIs with 7
different domains and their own Auth method and routes.
We should have been more careful but it was easy to miss at the time. 
https://developers.greenhouse.io/

- Remove confusion around which domain we request

- Remove key verification
Ideally, we create an alias for each of them, stop asking for the
domain, and re-up verification

## Changes

Fixes
https://linear.app/nango/issue/NAN-2298/document-getintegration-in-sdk

- Document getIntegration in the sdk

…sed on changes in NangoHQ/integration-templates@8216083 by Khaliq. Commit message: fix(lever): fix typo (#137)

##Describe your changes

Added configuration for `ebay` and `ebay-sandbox` in providers.yaml
Added `ebay` to docs-v2.
Added `ebay` pages for Supported API groups in mint.json.
Added `ebay` and `ebay-sandbox`  SVG file in template-logos folder.
Consolidate Ebay docs pages

##Test

This provider has been used successfully in local development to connect
to Ebay Sandbox API and Ebay API and successfully call those endpoints
after authorizing using Nango. (Have not tested sync and actions)

---------

Co-authored-by: Samuel Bodin <[email protected]>
Co-authored-by: Khaliq <[email protected]>