Is there a way to invoke a flow within another flow?

[Anastasia]

Hi there,

Is there a way to trigger another flow within a flow? Whether inbuilt, or using a more custom way

Thanks,

Anastasia

 

[Pabblymember11]

Hey @Anastasia

I am sorry to say that the use case that you are trying to build is not possible.

 

[Anastasia]

Hi Supreme. Thank you for the response. Truthfully, I find that a bit surprising, as it is a principle of programming to be able to invoke functions within functions : D

Can you come up with a creative hack to do that with? Is there an API call to flows perhaps?

Alternatively, is this on your roadmap?

 

[Pabblymember11]

Hey @Anastasia

I don't think so there is any workaround available for the same. If we get any API for the same in the future, we will let you know.

 

[Pabbly$Rocks7]

The workaround that I have used is to trigger sequential Pabbly Webhooks from the external source, so however you are triggering the first Pabbly webhook, add a slight delay and then trigger the second Pabbly Webhook.

I agree with you that this is a huuuuge oversight by Pabbly Programmers. GoTo routines are commonplace in programming languages. The ability to do a GoSub to a different Pabbly connector and then return to continue from where the second was called from would be even better.

I also find it very surprising that a "GoTo" (another connector) at minimum has not already been implemented.

 

[Anastasia]

The workaround that I have used is to trigger sequential Pabbly Webhooks from the external source, so however you are triggering the first Pabbly webhook, add a slight delay and then trigger the second Pabbly Webhook.

I agree with you that this is a huuuuge oversight by Pabbly Programmers. GoTo routines are commonplace in programming languages. The ability to do a GoSub to a different Pabbly connector and then return to continue from where the second was called from would be even better.

I also find it very surprising that a "GoTo" (another connector) at minimum has not already been implemented.

For what it's worth, I did come to a solution: I used the API Pabbly step to trigger a webhook to another flow that starts with a simple API webhook, and carried over the data I needed. But it's an extra billable step and I'm not sure if it's worth using just for the sake of admin and rebuilding similar flows easily for multi-step flows.

@Pabbly please make this a feature, I promise you it'll get you lots of positive feedback and it'll be a lovely selling point for people considering your service. I'll be your beta tester . You know "build once, never do it again", "modular automation". It'll look great on marketing.

 

[Anastasia]

The workaround that I have used is to trigger sequential Pabbly Webhooks from the external source, so however you are triggering the first Pabbly webhook, add a slight delay and then trigger the second Pabbly Webhook.

I agree with you that this is a huuuuge oversight by Pabbly Programmers. GoTo routines are commonplace in programming languages. The ability to do a GoSub to a different Pabbly connector and then return to continue from where the second was called from would be even better.

I also find it very surprising that a "GoTo" (another connector) at minimum has not already been implemented.

And yeah, even more so, to store the results of a flow as variables (nay, store variables generally) would be life-changiiing

 

[Arshita]

Hello @Anastasia

We are sorry, but there is any workaround available for the same?

We are receiving a large number of requests for building new integrations and updating the existing ones.

To allow the app owners to ship their integrations faster, we have opened our developer's platform inside Pabbly Connect.

We would request you to let the app team know about the open developer's platform. So that they can use the developer platform to build and ship their integration faster. As long as the app teams have an API and Webhooks, the integration can be done through our app developers' platform.

The guide for creating their app integrations can be shared with the app teams along with the message.

Application Integration Guide for Developers

This article explains the process of integrating your apps in Pabbly Connect.

forum.pabbly.com

In the meantime, you can also submit your integration request on our roadmap. We prioritize the integrations based on the number of upvotes received for the application.

Pabbly Connect

Vote or request new Pabbly Connect features. Subscribe to get updates about new features from Pabbly Connect.

pabbly.hellonext.co

 

[Anastasia]

Sorry @Arshita, what do you mean by We are sorry, but there is any workaround available for the same?

Further above a colleague told me there isn't. I then found a way to do it, but it comes with drawbacks, as I mentioned.

This feature is not to do with external app integrations, but internal Pabbly functionality. I requested it as a core feature, as per your instruction.

 

[Arshita]

Sorry @Arshita, what do you mean by We are sorry, but there is any workaround available for the same?

I apologize for the mistake in my previous message.

What I meant to convey is that currently, there is no available workaround for the same. We understand the inconvenience this may have caused you and we assure you that we will keep you informed if there are any updates or solutions regarding this matter in the future.