Migrate from Zapier to Pipedream

Help
1

We’re considering to migrate our workflow from Zapier to Pipedream, but I find some issues, could you please explain if it’s possible to achieve the same thing like Zapier?

this is an example private app of Zapier with this structure I could:

  1. Specify my own authentication method
  2. Create my own triggers + actions
  3. I could select my private app in the trigger/action dropdown
    Screenshot from 2022-09-08 13-13-13
    Screenshot from 2022-09-08 13-13-13908×665 75.1 KB

We have many organizations and each organization will have their id in the webhook url eg: POST /api/{org_id}/webhook
I find that all the workflows created from a source will be cascaded when one workflow make a change to the trigger so we can’t reuse the source for different organizations.

The source listen to the event immediately once I deploy the code which doesn’t make sense for us, because we only want to listen to an event in the workflow where we select the organization we would want to setup the workflow.

2

Hi @jacksontong

Great questions! Happy to answer those for you.

  1. Specify my own authentication method

Yes, you can still integrate any app into Pipedream using the app prop in a Node.js step, custom action or custom trigger.

Here’s a short screencast on how to do that: https://youtu.be/rckGb8BbPuk

  1. Create my own triggers + actions

Yes, you can publish your own custom triggers and actions to your own account or organization using the Pipedream CLI tool.

Here’s a short tutorial to learn how to create and privately publish a custom action to your own account:

We call actions and triggers Components and the Component Development process is documented here: Overview - Pipedream

  1. I could select my private app in the trigger/action dropdown

After you’ve published your own action for example, just select the My Actions app in a new step to use them in your workflow:

CleanShot 2022-09-08 at 11.14.24
CleanShot 2022-09-08 at 11.14.241147×502 59.5 KB

A similar button called Use exisiting source is available when creating a trigger on your workflow for custom sources.

We have many organizations and each organization will have their id in the webhook url eg: POST /api/{org_id}/webhook
I find that all the workflows created from a source will be cascaded when one workflow make a change to the trigger so we can’t reuse the source for different organizations.

The source listen to the event immediately once I deploy the code which doesn’t make sense for us, because we only want to listen to an event in the workflow where we select the organization we would want to setup the workflow.

Could you specify this request in our public issue tracker as a Feature Request, I think this is great feedback for our webhooks design and we’re always looking to improve it: