├── .github └── ISSUE_TEMPLATE │ ├── action-request.md │ ├── app---service-integration.md │ ├── bug_report.md │ ├── feature_request.md │ └── trigger-request.md └── README.md /.github/ISSUE_TEMPLATE/action-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Action Request 3 | about: Request a new action to make it easier to work with a specific API 4 | title: "[ACTION]" 5 | labels: action, enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is there a specific app this action is for?** 11 | 12 | **Please provide a link to the relevant API docs for the specific service / operation.** 13 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/app---service-integration.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: App / Service Integration 3 | about: Request for a new app integration 4 | title: "[APP]" 5 | labels: app, enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Name of app / service** 11 | 12 | **Link to developer documentation** 13 | 14 | **Is lack of support preventing you from building workflows, or do you have a workaround?** 15 | 16 | **Are there specific actions, or triggers, you'd like to see for this app? Please let us know here or use the Action and Trigger issue templates to open requests for each!** 17 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/bug_report.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Bug report 3 | about: File bugs here 4 | title: "[BUG] " 5 | labels: bug 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Describe the bug** 11 | A clear and concise description of what the bug is. 12 | 13 | **To Reproduce** 14 | Steps to reproduce the behavior: 15 | 1. Go to '...' 16 | 2. Click on '....' 17 | 3. Scroll down to '....' 18 | 4. See error 19 | 20 | **Expected behavior** 21 | A clear and concise description of what you expected to happen. 22 | 23 | **Screenshots** 24 | If applicable, add screenshots to help explain your problem. 25 | 26 | **Desktop (please complete the following information):** 27 | - OS: [e.g. iOS] 28 | - Browser [e.g. chrome, safari] 29 | - Version [e.g. 22] 30 | 31 | **Smartphone (please complete the following information):** 32 | - Device: [e.g. iPhone6] 33 | - OS: [e.g. iOS8.1] 34 | - Browser [e.g. stock browser, safari] 35 | - Version [e.g. 22] 36 | 37 | **Additional context** 38 | Add any other context about the problem here. 39 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/feature_request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Feature request 3 | about: Suggest an idea for Pipedream 4 | title: "[FEATURE] " 5 | labels: enhancement 6 | assignees: '' 7 | 8 | --- 9 | 10 | **Is your feature request related to a problem? Please describe.** 11 | A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] 12 | 13 | **Describe the solution you'd like** 14 | A clear and concise description of what you want to happen. 15 | 16 | **Do you have a workaround?** 17 | Are you able to tackle the problem with an existing workaround, or can you not move forward without this feature? 18 | 19 | **Comparable features in other tools?** 20 | Is this feature or one like it available in another platform? If so, we'd love to hear what you like about that implementation. 21 | 22 | **Additional context** 23 | Add any other context or screenshots about the feature request here. 24 | -------------------------------------------------------------------------------- /.github/ISSUE_TEMPLATE/trigger-request.md: -------------------------------------------------------------------------------- 1 | --- 2 | name: Trigger Request 3 | about: Need to run a workflow on a specific event, like every time a new PR is opened 4 | on Github? Request it here! 5 | title: "[TRIGGER]" 6 | labels: enhancement, trigger 7 | assignees: '' 8 | 9 | --- 10 | 11 | **Is there a specific trigger this trigger is for?** 12 | 13 | **Please provide a link to the relevant API docs for the specific service / operation this trigger is tied to.** 14 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | ## Pipedream Roadmap 2 | 3 | This repo serves as a public roadmap for [https://pipedream.com](https://pipedream.com). You can view the current roadmap at [this project board](https://github.com/PipedreamHQ/roadmap/projects/1). 4 | 5 | This isn't the full Pipedream backlog, but a public view into some of the major features we're working on. We may ship things that aren't on this list, and may not be able to tackle every request made here. 6 | 7 | We're eager to build a developer integration platform that solves real problems for you, and we want to respond directly to your feedback. We use Github Issues to track this feedback. 8 | 9 | If you don't know whether you've found a bug or want to talk to our team about a new feature in more depth, please [join our public Slack community](https://pipedream.com/community) and send us a note. 10 | 11 | While Pipedream publishes some open source tools (for example, the [SDK](#sdk)), the Pipedream platform itself is not open source. This repo contains no source code, but provides you visibility into what we're working on and gives you a way to suggest your own ideas for how to improve Pipedream. 12 | 13 | ## Adding a new issue 14 | 15 | Before adding an issue, please search the [existing issues](https://github.com/PipedreamHQ/roadmap/issues) to see if a similar request already exists, or reach out on our [Slack community](https://pipedream.com/community). 16 | 17 | If an issue already exists, please [add a reaction](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/about-conversations-on-github) to that request or comment with your specific use case. This helps us prioritize requests based on demand. 18 | 19 | If an issue _doesn't_ yet exist, please use these templates to create one: 20 | 21 | **[Click here to request a new feature](https://github.com/PipedreamHQ/roadmap/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=)** 22 | 23 | **[Click here to report a bug](https://github.com/PipedreamHQ/roadmap/issues/new?assignees=&labels=bug&template=bug_report.md&title=)** 24 | 25 | **[Click here to request a new app integration](https://github.com/PipedreamHQ/roadmap/issues/new?assignees=&labels=app&template=app---service-integration.md&title=%5BAPP%5D)** 26 | 27 | **[Click here to request a new action](https://github.com/PipedreamHQ/roadmap/issues/new?assignees=&labels=action%2C+enhancement&template=action-request.md&title=%5BACTION%5D)** 28 | 29 | **[Click here to request a new trigger](https://github.com/PipedreamHQ/roadmap/issues/new?assignees=&labels=enhancement%2C+trigger&template=trigger-request.md&title=%5BTRIGGER%5D)** 30 | 31 | ## Security disclosures 32 | 33 | If you'd like to report a suspected vulnerability or security issue, or have any questions about the security of the product, please contact us at **security@pipedream.com** directly. 34 | 35 | ## SDK 36 | 37 | If you have a feature request or bug to file for the Pipedream SDK, please do so in the [SDK repo](https://github.com/PipedreamHQ/sdk). 38 | 39 | --------------------------------------------------------------------------------