Adding Shortcut source connector


Check if Airbyte wants to add a source connector for Shortcut and inquire about its status


there have been some sporadic requests to add a source for Shortcut ( across the ages, and I was going to take that on, but wanted to check if that’s something Airbyte would want before continuing. There is an issue but it was converted to <New Source: Shortcut · airbytehq/airbyte · Discussion #33152 · GitHub discussion>, and it’s not on the Community Contributions Connectors board

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want to access the original thread.

Join the conversation on Slack

["shortcut-source-connector", "community-contributions", "airbyte"]

Based on the information provided in the extracts, Airbyte is open to contributions for new connectors, especially those built with the Low-Code CDK or Connector Builder, as these connectors are easier to maintain. However, due to project priorities, not all contributions may be accepted at this time source. If you’d like to build a new connector for Shortcut, you can follow the guide on building new connectors here. Once you’ve built the connector, you can submit it to Airbyte following the steps outlined here. However, before you proceed, it would be advisable to discuss this with the Airbyte team or community, especially since the issue was converted to a discussion. You can do this by commenting on the existing discussion or creating a new one. This will help ensure that your contribution aligns with Airbyte’s current priorities and that it will be accepted once completed.

I should take a look at that community connectors board huh.

If you build it as a low-code connector (I strongly recommend the connector builder), and then export it into a pull request — we’ll be happy to support you through it, sure.