-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
[source-linkedin-ads] Lead forms & Lead form responses new streams #52047
[source-linkedin-ads] Lead forms & Lead form responses new streams #52047
Conversation
@kev-datams is attempting to deploy a commit to the Airbyte Growth Team on Vercel. A member of the Team first needs to authorize it. |
hello @natikgadzhi @marcosmarxm, FYI following this previous PR 🙏 |
…-leads-streams # Conflicts: # airbyte-integrations/connectors/source-linkedin-ads/metadata.yaml # airbyte-integrations/connectors/source-linkedin-ads/pyproject.toml # docs/integrations/sources/linkedin-ads.md
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I think the CATs are failing because our sandbox does not have the data in the new streams. Can you edit the |
…s' into source-linkedin-ads-leads-streams
Head branch was pushed to by a user without write access
@natikgadzhi done ✅ |
@DanyloGL can you please test this one? |
airbyte-integrations/connectors/source-linkedin-ads/integration_tests/expected_records.jsonl
Outdated
Show resolved
Hide resolved
Really nice work @marcosmarxm and @kev-datams. @kev-datams thank you for being so patient with us and so generous with your contributions <3 |
Thank you for reviewing, this is clearly a win-win 🙂 |
What
This Pull Request aims in proposing a first version of the
LinkedIn Leads
streams based on official documentation.It follows this PR adapted for low-code and merged in LinkedIn Ads connector.
How
This PR adds 2 base streams in existing
LinkedIn Ads
connector:The required permission on LinkedIn is
r_marketing_leadgen_automation
according to this doc bloc.Review guide
Limits & considerations
section)User Impact
User will have access to 2 streams of a new connector.
As explained in the
Limits & considerations
section of the Documentation and due to low-code capabilities limitations:path
Incremental sync
is not supported because of specific query param expected by LinkedIn API (eg:submittedAtTimeRange=(start:1711407600000,end:1711494000000)
)Can this PR be safely reverted and rolled back?