Skip to content

source-twentycrm contribution from lucasagon#75268

Closed
Lucas Almeida Gonçalves (lucasagon) wants to merge 1 commit intoairbytehq:masterfrom
lucasagon:lucasagon/builder-contribute/source-twentycrm
Closed

source-twentycrm contribution from lucasagon#75268
Lucas Almeida Gonçalves (lucasagon) wants to merge 1 commit intoairbytehq:masterfrom
lucasagon:lucasagon/builder-contribute/source-twentycrm

Conversation

@lucasagon

What

This PR adds a new connector for source TwentyCRM (source-twentycrm).

Contributor-provided connector description:

TwentyCRM with connection to people, companies and opportunities REST endpoints.

The contributor provided the following description of the change:

I use inputs for the domain and bearer api. I'm using a self-hosted instance of TwentyCRM.

Details

Expand for list of spec properties and streams

Configuration

Input Type Description Default Value
api_key string API Key.
domain string domain.

Streams

Stream Name Primary Key Pagination Supports Full Sync Supports Incremental
people DefaultPaginator
companies DefaultPaginator
opportunities DefaultPaginator

Reviewer checklist

  • Consider how the connector handles pagination (docs).
  • Help the contributor upload an icon that follows our icon design guidelines
  • Click into the CI workflows that wait for a maintainer to run them, which should trigger CI runs

@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@octavia-bot octavia-bot bot marked this pull request as draft March 21, 2026 01:19
@octavia-bot
Copy link
Contributor

octavia-bot bot commented Mar 21, 2026

Note

📝 PR Converted to Draft

More info...

Thank you for creating this PR. As a policy to protect our engineers' time, Airbyte requires all PRs to be created first in draft status. Your PR has been automatically converted to draft status in respect for this policy.

As soon as your PR is ready for formal review, you can proceed to convert the PR to "ready for review" status by clicking the "Ready for review" button at the bottom of the PR page.

To skip draft status in future PRs, please include [ready] in your PR title or add the skip-draft-status label when creating your PR.

@github-actions
Copy link
Contributor

👋 Welcome to Airbyte!

Thank you for your contribution from lucasagon/airbyte! We're excited to have you in the Airbyte community.

If you have any questions, feel free to ask in the PR comments or join our Slack community.

💡 Show Tips and Tricks

PR Slash Commands

As needed or by request, Airbyte Maintainers can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
  • /run-connector-tests - Runs connector tests.
  • /run-cat-tests - Runs CAT tests.
  • /run-regression-tests - Runs regression tests for the modified connector(s).
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
  • /publish-connectors-prerelease - Publishes pre-release connector builds (tagged as {version}-preview.{git-sha}) for all modified connectors in the PR.
  • /ai-review - AI-powered PR review for connector safety and quality gates.
  • /force-merge reason="<A_GOOD_REASON>" - Force merges the PR using admin privileges, bypassing CI checks. Requires a reason.

Tips for Working with CI

  1. Pre-Release Checks. Please pay attention to these, as they contain standard checks on the metadata.yaml file, docs requirements, etc. If you need help resolving a pre-release check, please ask a maintainer.
    • Note: If you are creating a new connector, please be sure to replace the default logo.svg file with a suitable icon.
  2. Connector CI Tests. Some failures here may be expected if your tests require credentials. Please review these results to ensure (1) unit tests are passing, if applicable, and (2) integration tests pass to the degree possible and expected.
  3. (Optional.) BYO Connector Credentials for tests in your fork. You can optionally set up your fork with BYO credentials for your connector. This can significantly speed up your review, ensuring your changes are fully tested before the maintainers begin their review.
📚 Show Repo Guidance

Helpful Resources

📝 Edit this welcome message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Inactive

Development

Successfully merging this pull request may close these issues.

3 participants