> ## Documentation Index > Fetch the complete documentation index at: https://kwala.network/docs/llms.txt > Use this file to discover all available pages before exploring further. # Configure workflow > Configure triggers, actions, and settings for your workflow After creating a workflow, you need to configure its triggers, actions, and execution settings. This guide walks you through each configuration step in the Workflow Builder. ## Prerequisites * Completion of the steps in [Create workflow](https://kwala.network/docs/workflow-builder/create-workflow.md). ## Configuration steps Configuring a workflow involves three steps: 1. **Configure triggers**: Define when and how your workflow activates 2. **Configure actions**: Specify what your workflow does when triggered 3. **Configure execution mode**: Choose how actions are processed ## Step 1: Configure triggers Triggers determine when your workflow activates. In the Workflow Builder, you'll configure execution settings that control trigger behavior. ![Trigger configuration settings](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/configure-triggers-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=190f68c9ee5ab7fc42ff65d5f7120127) ### Required trigger fields The required fields for trigger configuration are **Execute after**, **Repeat every**, and **Expires in**. **Execute after** Defines when the workflow should start executing. Choose from the following options: * **Immediate**: Workflow executes as soon as it is deployed and activated. * **Timestamp**: Workflow executes at a specific date and time * **Event**: Workflow executes when a specified on-chain event occurs * **Oracle price**: Workflow executes when a token reaches a target price * **Block number**: Workflow executes at a specific block height When you add trigger options, the **Workflow Builder** automatically adds additional configuration steps. For example, if you select **Oracle price** as a trigger, the workflow builder displays a **Trigger Source Configuration** where you specify the target price and select a token from the dropdown, as shown: ![Oracle price trigger source configuration](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/oracle-price-trigger-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=255f24d0f5482f07df0fea189d6d5fe2) **Repeat every** Determines if and when the workflow should repeat. Choose from the following options: * **Time interval**: Workflow repeats at regular intervals. For example, every hour or daily * **Oracle price**: Workflow repeats when price conditions are met again * **Event**: Workflow repeats each time the specified event occurs * **N/A**: Workflow executes only once and does not repeat Similar to the **Execute after** trigger, selecting a **Repeat every** trigger displays additional configuration fields. For example, if you select **Event** as the **Repeat every** trigger, the builder displays a Recurring Source Configuration as shown: ![Recurring source configuration for event-based repeat](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/trigger-config-repeat-after-event-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=4afe47f8ba1620fa4e36c44ee897388e) * **Recurring Contract**: The smart contract address to monitor for recurring events. For example, `0x49e833337ece7afe375e44f4e3e8481029218e5c`. * **Recurring Chain ID**: The blockchain network where the contract is deployed, such as `1` for Ethereum mainnet. * **Smart Contract (Optional)**: Paste Solidity contract code or upload a `.sol` file to automatically extract the ABI * **Recurring Source Contract ABI**: The contract's ABI for parsing events. This is auto-populated if the contract is verified on the blockchain or if you upload a contract file. * **Recurring Event Name**: Select the event to listen for from the dropdown. For example, `Transfer(address,address,uint256)`. * **Recurring Event Filter**: Filter criteria for the event. Use `NA` if no filter is needed. > [!TIP] > > To find oracle contract addresses for different price feeds, visit the [Chainlink Data Feeds](https://data.chain.link/feeds) directory. **Expires in** Sets when the trigger expires. Use the calendar icon to select the expiry date and time. The Workflow Builder automatically converts this into a Unix timestamp. ![Expires in calendar picker](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/calendar-date-picker-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=552d631158f08d884e2e6223a7502e90) Once you've configured your workflow triggers, Select **Next** to continue to action configuration. ## Step 2: Configure actions Actions define what your workflow does when the trigger activates. You can only add up to 10 actions per workflow. ### Required fields for all actions Every action requires the following fields: * **Action Name**: A descriptive identifier for the action (for example, `transfer_funds` or `send_notification`) * **Action Type**: The type of operation to perform. Kwala supports three action types: * **POST**: Make an API call to an external endpoint * **CALL**: Call a function on an existing smart contract * **Deploy**: Deploy a new smart contract The workflow builder prompts you to fill out additional required fields depending on the action type you select. **POST API call** Use the **POST** action type to send HTTP requests to external APIs, webhooks, or notification services. ![Action configuration settings](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/configure-actions-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=9b8db7d721939cefd1ca9752f2e4c706) Required fields for POST actions: * **Webhook URL**: The URL to send the request to. For example, `https://api.telegram.org/bot7754368882:AAHS4KbbOkl5rEHoBBIR8eljgwq2PARYLyY/sendMessage` * **API Payload**: The JSON data to include in the request body. You can pass both fixed values and event parameters in a POST action. * **Retries Until Success**: Number of retry attempts if the request fails. When adding target parameters for your action, you can use the event parameters from your trigger. Use `re.event(0)`, `re.event(1)`, `re.event(2)`, or any other index to reference values from the triggering event. **Example POST configuration** The following example shows a POST action where both fixed values and event parameters can be used when calling web2 APIs. ```yaml theme={null} - Name: notification_action Type: post APIEndpoint: https://your-endpoint.example.com/webhook APIPayload: message: Transfer detected # fixed value token: ETH # fixed value amount: re.event(2) # event parameter RetriesUntilSuccess: 5 ``` **Web3 smart contract function** Use the **Web3 Call** action type to interact with an existing smart contract by calling one of its functions. ![CALL action configuration](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/configure-call-actions-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=8bc10f212d202d25b382eb1119e299a8) Required fields for Web3 Call actions: * **Target Contract**: The address of the smart contract to interact with. For example, `0x65b2b850fee0e0c13d956ab5...` * **Function**: The function signature to call. For example, `function updateNFT(string memory userId, uint256 points)` * **Chain ID**: The blockchain network where the contract is deployed. Select from the dropdown * **Params**: The parameters to pass to the function. You can use fixed values or reference event data dynamically with re.event(0), re.event(1), etc. Enter each parameter on a separate line. * **Retries Until Success**: Number of retry attempts if the call fails **Example Web3 Call configuration** ```yaml theme={null} - Name: transfer_funds Type: call TargetContract: 0x0f51bb10119727a7e5ea3538074fb341f56b09ad TargetFunction: function transfer(address recipient, uint256 amount) TargetParameters: - re.event(0) # dynamic - recipient address from triggering event - 100 # fixed - transfer amount ChainID: 1 RetriesUntilSuccess: 5 ``` **Deploy smart contract** Use the **Deploy** action type to deploy a new smart contract to a blockchain network. ![Deploy action configuration](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/configure-deploy-action-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=e589e542f464d8d629522452fafe61ac) Required fields for Deploy actions: * **Chain ID**: The blockchain network where the contract will be deployed. Select from the dropdown * **Smart Contract**: Upload a `.sol` file or paste your Solidity contract code directly. This is used to extract the bytecode and ABI * **Bytecode**: The compiled contract bytecode in hexadecimal format (for example, `0x608060405234801561001057600080fd5b50...`). This is auto-populated if you upload a contract file * **ABI Encoded**: The contract's ABI encoded in base64 format (for example, `W3siaW5wdXRzIjpbXSwibmFtZSI6ImV4YW1wbGUiLCJvdXRwdX...`). This is auto-populated if you upload a contract file * **Retries Until Success**: Number of retry attempts if deployment fails. ### Adding multiple actions Select **Add Action** to include additional actions in your workflow. You can add up to 10 actions per workflow. Each action can be a different type, allowing you to combine contract calls, API requests, and deployments in a single workflow. Select **Next** when you've finished configuring all actions. > [!NOTE] > > For more detailed information about action types and advanced parameters, see [Working with actions](https://kwala.network/docs/concepts/actions.md). ## Step 3: Configure execution mode Choose how your actions should be processed using the **Execution Mode** dropdown: * **Sequential**: Actions execute one after another in order. Use this when later actions depend on the results of earlier actions. * **Parallel**: All actions execute simultaneously. Use this when actions are independent of each other and speed matters. ![Execution mode selection](https://mintcdn.com/kwala-1f7da9fb/akerdb841SeH-41k/images/workflow-builder/configure-workflow/configure-execution-mode-new.png?fit=max\&auto=format\&n=akerdb841SeH-41k\&q=85\&s=303aaa88519062629e6c8abc03c47d45) After selecting your execution mode, the builder displays a **Workflow Summary** that shows an overview of the configuration. The summary includes: * **Workflow Name**: The name you assigned to your workflow * **Trigger Contract**: The smart contract address being monitored * **Actions Count**: The total number of actions configured * **Execution Mode**: Whether actions run in parallel or sequential order ## Review and create workflow Review the summary to verify your configuration is correct. Once you're satisfied, select **Create Workflow** to generate your workflow. After selecting **Create Workflow**, you should see a success message: **"Workflow created - Your workflow has been generated and loaded to the editor"**. The Workflow Builder generates a complete YAML automation script and opens it in the Workflow Editor for review. From there, you can make any additional edits before deploying. ## Next steps > **[Deploy workflow](https://kwala.network/docs/workflow-builder/deploy-workflow.md)** > > Deploy your workflow to the network > **[Working with triggers](https://kwala.network/docs/concepts/triggers.md)** > > Learn more about trigger types > **[Working with actions](https://kwala.network/docs/concepts/actions.md)** > > Explore action configuration options > **[Workflow templates](https://kwala.network/docs/concepts/workflow-templates.md)** > > Use pre-built workflow templates This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.