Pick a script or flow to be triggered

{#if script_path === undefined && is_flow === false}

{/if}

Pick a database to connect to

{#if postgres_resource_path}

Choose the types of database transactions that should trigger a script or flow. You can select from Insert, Update, Delete, or any combination of these operations to define when the trigger should activate.

Select the tables to track. You can choose to track all tables in your database, all tables within a specific schema, specific tables in a schema, or even specific columns of a table. Additionally, you can apply a filter to retrieve only rows that do not match the specified criteria.

Basic

Choose the relations to track without worrying about the underlying mechanics of creating a publication or slot. This simplified option lets you focus only on the data you want to monitor.

Advanced

Select a specific publication from your database to track, and manage it by creating, updating, or deleting. For slots, you can create or delete them. Both non-active slots and the currently used slot by the trigger will be retrieved from your database for management.

{ replication_slot_name = '' }} disabled={!can_write} let:item > {#if selectedSlotAction === 'create'}

{:else} {/if}

{ if (selectedPublicationAction === 'create') { selectedTable = 'specific' publication_name = `windmill_publication_${random_adj()}` relations = [{ schema_name: 'public', table_to_track: [] }] return } publication_name = '' relations = [] transaction_to_track = [] }} let:item > {#if selectedPublicationAction === 'create'}

{:else} {/if}

{/if}