Inline actions make it easy to work with “blocks” of actions, which are all linked together and organized in a group. You can create a conditional block with the Pushbot: Start another Pushbot action.
Blocks help organize steps, and make them more portable. A block can have its own dependencies and conditions: so if the dependencies are met, the entire block begins, rather than needing to configure each step within the block manually.
Envision a process where a user picks between three options. Based on the choice, one of three paths of an automation start. Many dependencies and conditions must be configured to enable this. And if there are any changes to the process in the future, reconfiguring the dependencies and conditions will take extra time.
Check out the following video for a quick overview of conditional blocks:
The Pushbot: Start another Pushbot action is the conditional block action.
- From the builder screen, add an action and select Pushbot: Start another Pushbot.
Select which process to start. Select
Build inlineto configure a process inline, from scratch. Select
Use Pushbot by name,
fieldto link to, embed, and start an existing process in the block.
- For more help on configuring the rest of the block, check the How to configure this action section for Pushbot: Start another Pushbot.
You can create new blocks and add your own steps to them, or reference an existing Pushbot in a conditional block, and mirror its steps within your process.
If you want to organize tasks and make dependencies and conditions easier to manage,
Build inline is recommended. This option gives you the power to configure the block, but without needing to manage a separate Pushbot—everything is managed inline.
If you build inline, the subprocess inherits all default field permissions or retroactive field permission changes because it is managed by the parent Pushbot.
If you have a Pushbot that’s already built and ready to start, you can reference it by name, ID, or field. This will be a good option for Pushbot’s owned by another team member, or when processes are managed independently to take advantage of versioning, or so specific permissioning can be configured.
If you reference a Pushbot by name, ID, or field, you are referencing a separate, published Pushbot on your team. Edits to the inline actions affect the actual Pushbot process you’ve embedded.
- Users with view permissions on a Pushbot can add that Pushbot, but cannot make changes to it. They will be able to use the steps as part of their process, set up conditions and dependencies, and see outputs, but cannot change the steps themselves.
- Users with edit permissions on a Pushbot can add that Pushbot, and make changes to the process inline.
💡Tip: The published version of the Pushbot is always used when using a Pushbot by name, ID, or field
All field values in inline actions are available in the parent Pushbot. When a conditional block completes, it outputs fields as normal. Each field is accessible directly by the field reference name.
If something’s not working as expected, or you’re looking for suggestions, check through the options below.
You can nest as many inline actions as you wish. After the third level of nested actions, the actions are automatically collapsed and cannot be edited inline. To edit inline actions that is nested more than 3 levels, select it to open it in a full view.