This topic was automatically generated from Slack. You can find the original thread here.
Hi - If we want to develop a connector in house, how do we get it published on Pipedream?
This topic was automatically generated from Slack. You can find the original thread here.
Hi - If we want to develop a connector in house, how do we get it published on Pipedream?
Hi - If we want to develop a connector in house, how do we get it published on Pipedream?
If you want to develop a connector (integration/component) in-house and have it published on Pipedream, here’s how you can approach it: 1. Develop the Connector (Component) Locally - Pipedream connectors are called “components” and are written in Node.js (or Python for code steps). - You can develop triggers and actions as components using the Pipedream component API. - Test your component locally and in your own Pipedream account. 2. Publishing Your Connector - If you want your connector to be available to all Pipedream users (published in the public registry), you’ll need to submit it to Pipedream for review and publication. - Currently, Pipedream manages the publishing process for public components. You can contribute your component by opening a pull request to the Pipedream Components GitHub repo, or by contacting Pipedream support for guidance. 3. Get Help and Guidance - For questions about component development or the publishing process, visit Pipedream Support. - You can also refer to the Pipedream Connect component docs for more details on building and contributing components. Summary Steps: - Build and test your connector/component in your Pipedream account. - Submit your component to Pipedream (usually via GitHub PR or by contacting support). - Pipedream will review, test, and publish it if it meets requirements. If you need more specific guidance or want to discuss your use case, contact Pipedream Support.
If we don’t publish our connector, would we still be able to use our custom connector?
Yes, you can use your custom connector (component) in your own Pipedream workspace without publishing it to the public registry. When you develop a custom component in-house, you can publish it privately to your workspace using the Pipedream CLI. Once published, your custom tools will appear alongside public components for your workspace and can be used in your workflows and with Connect APIs. You do not need to publish your connector publicly to use it internally. Only if you want to make it available to all Pipedream users do you need to submit it for public publication. For more details, see the Using Custom Tools documentation.
Pipedream doesn’t work with apps that are not integrated
Like we can’t refresh the tokens and stuff
Gotcha. Just trying to see what our options our.