TriggerX Safe Automation Wallet

Overview

The TriggerX Wallet integration allows fully automated on-chain execution for any jobs you create on TriggerX. Once your Safe (formerly Gnosis Safe) is connected and authorized, TriggerX can execute transactions on your behalf according to the automation rules you configure. This authorization is a one-time setup per Safe. After that, your Safe becomes automation-ready.

What Is the TriggerX Safe Automation Wallet?

The TriggerX Wallet integration extends your Safe wallet with automation capabilities, letting TriggerX:

  • Trigger on-chain actions when job conditions are met (time, events, conditions)

  • Execute your predefined contract calls

  • Manage scheduled or recurring tasks securely

TriggerX never holds your funds. Your Safe simply permits TriggerX to perform the specific actions you configure.

Supported Wallet Types

TriggerX currently supports:

  • Safe (Gnosis Safe) wallets only

This includes both single-sig and multisig Safe accounts.

Supported Networks

TriggerX Safe Module is available on the following EVM networks:

  • OP Sepolia

  • Base Sepolia

  • Arbitrum Sepolia

  • Arbitrum One

Support for additional networks may be added over time.

Importing Your Safe Wallet on TriggerX

Before enabling the TriggerX Module, ensure the following:

Wallet Ownership

  • The connected wallet must be the owner of the Safe.

Correct Network

  • The Safe must exist on the currently selected chain.

  • The TriggerX Module must be deployed on that chain. (The app automatically loads the correct module address per network.)

Import Flow: Single-Sig vs Multisig Safe

TriggerX provides two different flows depending on your Safe configuration.

Importing a Single-Sig Safe Wallet

This is the simplest flow. Since the connected wallet is the sole owner, all steps execute instantly.

  1. Enter your Safe address on the TriggerX platform.

  2. Sign the module-enable message (EIP-712).

  3. Confirm the on-chain transaction — the connected wallet directly executes it.

  4. Done.

    • The module is enabled immediately.

    • Your Safe appears in your wallet list.

Importing a Multisig Safe Wallet

For a multisig Safe, TriggerX prepares a proposal that requires confirmation from other Safe owners.

  1. Enter your Safe address on the TriggerX platform.

  2. Sign the module-enable message (EIP-712).

  3. A proposal/transaction request is created instead of immediate execution.

  4. The user receives a Safe App link (or equivalent) to:

    • Review the pending module-enable transaction

    • Sign it

    • Ask other Safe owners to sign as well

  5. Once all required signatures are collected and the transaction is executed on-chain:

    • Return to the TriggerX UI

    • Click Refresh to update the module status

  6. Done.

    • The module is now enabled across all multisig owners.

Recommended Setup

To avoid friction, we recommend:

Prefer Single-Sig Safes for Simplicity

  • Enabling the module requires only one transaction

  • Executes instantly without needing additional approvals

For Multisigs

  • Ensure all required owners can co-sign promptly

  • Coordinate availability before starting the process

Keep Sufficient Native Tokens

  • For execution gas

  • For multisig proposal creation (where applicable)

Avoid Network Switching

Switching networks mid-flow can invalidate detection steps.

How to Enable the TriggerX Module

Import Safe

Navigate to Safe Wallet Management → Import Safe Wallet, and enter your Safe address.

Sign Step

You will be prompted to sign an EIP-712 typed data message using the Safe SDK. This validates ownership and initializes the module enable workflow.

Execute Step

Execution differs depending on the Safe configuration:

  • Single-Sig Safe

    • The transaction is broadcast immediately

    • The module is enabled instantly

  • Multisig Safe

    • A proposal is submitted to the Safe Transaction Service

    • Other owners must confirm it

    • Once the threshold is met, the module is executed on-chain

After successful execution:

  • Your Safe is stored locally on the TriggerX app

  • It appears in your Safe wallet list

  • Module status is cached but can be refreshed anytime

Multisig Behavior Explained

For a multisig Safe:

  • If threshold > 1, enabling the module becomes a proposal

  • The proposal must be confirmed by enough owners (as per the Safe threshold)

  • The app provides a “Queue” link that opens the Safe web interface to view and approve the transaction (if supported on the chain)

This ensures full transparency and adherence to multisig trust guarantees.

Safe Wallet Execution Flow

What You Can Do With the TriggerX Wallet

TriggerX integrates directly with Safe (Gnosis Safe) to provide secure, reliable, and permissioned automation for both individuals and teams. Safe wallets offer a programmable, modular, and multisig-secure environment, making them ideal for on-chain automation where security and governance are essential.

Key Use Cases for Using a Safe with TriggerX

1. Team-Controlled Automation (Multisig Automations)

  • Perfect for DAOs, protocols, and teams requiring shared control.

  • All automated actions still follow Safe’s signature thresholds.

  • Ensures no single party can unilaterally automate high-value transactions.

2. Secure Execution of Automated DeFi Actions

  • Automate recurring operations like:

    • Reward distribution

    • Liquidity rebalancing

    • Fee claims

    • Portfolio shifts

  • All executed with Safe’s security guarantees.

3. No Private Keys Exposed

  • Your Safe holds the contract authority, not an EOA.

  • TriggerX only triggers approved jobs, never controls your wallet.

4. Workflow Automation Without Losing Governance

  • Multisig owners approve module enablement once.

  • After that, TriggerX executes only the jobs you define.

  • Full transparency via Safe Transaction Service.

5. Ideal for High-Value Accounts

  • Institutions

  • Projects with treasury funds

  • Protocol-owned liquidity

  • Investors requiring automation without trust trade-offs

Safe + TriggerX = Automation with governance + security + transparency.

Security Considerations

TriggerX follows a strict least-authority design, ensuring the module only receives the minimal permissions required to automate your jobs. To maintain a secure setup, users should keep the following in mind:

  • Double-check the module address and chain before signing

  • Review Safe transaction permissions periodically

  • User maintains full ownership and control of their Safe

  • Module only executes the jobs you create and approve

The TriggerX Module cannot take custody of your assets; it can only perform the specific, scoped actions authorized by your Safe and defined in your jobs.

Terminology

Safe: A modular multisig smart-contract wallet by Safe (Gnosis Safe).

Proposal: A multisig transaction is awaiting confirmations from Safe owners before execution.

PreviousReferencesNextCreate Your First Time Based Job

Last updated