This topic was automatically generated from Slack. You can find the original thread here.
i want to use step variable of a trigger in workflow available 2 level down
To access a step variable from a trigger in a step that’s two levels down, you can use the steps object. For example, if your trigger step is named trigger_step, you can access its variable like this: const variableFromTrigger = steps.trigger_step.variable_name; Replace trigger_step with the name of your trigger step and variable_name with the name of the variable you want to access.
my second workflow is a gsheet flow which does not return the parent step to its child
To pass data from a parent step to a child step in a workflow that involves Google Sheets, you can use the steps object to reference the output of the parent step. For example, if your parent step is named parent_step, you can access its output like this: const dataFromParent = steps.parent_step.$return_value; Replace parent_step with the name of your parent step. If you’re still having trouble, please provide more details about your workflow, such as the specific steps involved and their names, so I can help you better.
where i can find the name of parent step
To find the name of a parent step in your Pipedream workflow, you can look at the workflow editor in the Pipedream UI. Each step in the workflow has a name displayed below the step’s title. You can also click on the step and check the “Step Name” field in the step settings on the right side of the editor.
make a workflow synchronous
Pipedream workflows are designed to be asynchronous by nature. Each step in a workflow runs independently and in parallel, allowing for faster execution. However, if you need to enforce a specific order of execution for certain steps, you can use the output of a previous step as input for the next step. This will create a dependency between the steps, ensuring that the second step waits for the completion of the first step before executing. Keep in mind that this approach might not be suitable for all use cases, and the asynchronous nature of Pipedream workflows is intended to provide better performance and flexibility.
make a workflow synchronous i.e. it should wait for previous http request to be fulfilled before running new
In Pipedream workflows, steps are executed in sequence, so they already wait for the previous step to complete before running the next step. If you have an HTTP request in one step, the next step will not run until the HTTP request is completed. For example, if you have two HTTP request steps, http_request_1 and http_request_2, the workflow will execute http_request_1 first, wait for it to complete, and then execute http_request_2. If you need to use the output of the first HTTP request in the second request, you can access it using the steps object: const dataFromPreviousRequest = steps.http_request_1.$return_value; Replace http_request_1 with the name of your first HTTP request step.
run trigger in synchronous manner
I want to run triggers in synchronous manner
Triggers in Pipedream workflows are designed to be asynchronous and event-driven. They initiate the workflow when an event occurs, such as an HTTP request, a scheduled time, or an app-based event. You cannot run triggers in a synchronous manner. However, the steps following the trigger in your workflow are executed in sequence. Each step waits for the previous step to complete before executing. If you need to enforce a specific order of execution for certain steps, you can use the output of a previous step as input for the next step, creating a dependency between the steps.