Skip to main content
Build dynamic workflows by chaining single actions together programmatically. This approach gives you full control over execution flow with conditional logic and runtime decision-making.

What are Programmatic Actions?

Programmatic actions let you build browser automation workflows using code instead of the visual workflow builder. You write Python (or other languages) to orchestrate individual browser actions, giving you complete control over the execution flow.

How It Works

The basic pattern involves:
  1. Create a session to maintain browser state across actions
  2. Execute actions sequentially using the same session ID
  3. Pass data between actions using variables
  4. Add conditional logic based on action results
  5. Terminate the session when complete

Key Advantages

Full Control

Complete programmatic control over execution flow and logic

Dynamic Logic

Make decisions at runtime based on previous action results

Easy Integration

Seamlessly integrate into existing codebases and applications

No Pre-Definition

Build workflows on-the-fly without pre-configuring in the dashboard

When to Use Programmatic Actions

Perfect when you need to make decisions at runtime based on the results of previous actions or external data.Example: Check if a user is logged in, and only perform login if needed.
Use when your workflow requires branching, loops, or complex conditional logic that can’t be predefined.Example: Process a variable number of items based on what’s found on the page.
Ideal when the workflow is deeply integrated with your application logic and needs to interact with other systems.Example: Fetch data from your database, use it in browser actions, then save results back to your database.
Best when you want full programmatic control and prefer Git-based version control over dashboard-based management.Example: Version control your automation alongside your application code.
Use when you need sophisticated error handling, retries, or fallback strategies tailored to your use case.Example: Implement exponential backoff retries with custom retry logic.

Limitations

While powerful, programmatic actions have some tradeoffs:
  • Requires writing and maintaining code
  • No visual representation of the workflow
  • Debugging requires custom logging
  • Changes require code deployment
For stable, repeatable workflows that don’t require runtime decisions, consider using the Visual Workflow Builder instead.

Detailed Guides

Comparison with Other Approaches

FeatureProgrammatic ActionsVisual Workflow Builder
ControlFull programmatic controlVisual configuration
Conditional LogicRuntime decisions with codePre-configured conditions
IntegrationEasy integration with appsStandalone workflows
Version ControlGit-basedDashboard-based
DebuggingCustom logging neededBuilt-in execution logs
Best ForDynamic, integrated workflowsStable, repeatable tasks

API Reference

Need Help?

For questions or support with programmatic actions, contact us at [email protected].