CRATEDB n8n INTEGRATION: AUTOMATE CRATEDB WITH N8N

The Execute Query action is your Swiss Army knife for CrateDB automation—it lets you run any valid SQL statement against your database directly from an n8n workflow. This is the most flexible action available, perfect for complex queries that go beyond simple inserts or updates.

Key parameters:

• Credential to connect with: Required dropdown to select your stored CrateDB account credentials. This determines which database instance receives your query.
• Operation: Required dropdown set to "Execute Query" to indicate you're running a custom SQL statement.
• Query: Required multiline text input where you write your SQL statement. This accepts any valid CrateDB SQL syntax including SELECT, DELETE, CREATE TABLE, or complex JOINs.
• Additional Fields: Expandable section for optional configurations that may be needed for specific use cases.

Use cases: This action excels when you need to run SELECT queries that feed data into subsequent workflow steps—for example, fetching all orders from the last 24 hours to process in a loop. It's also ideal for DELETE operations with complex WHERE clauses, running aggregate queries for reports, or executing DDL statements like creating temporary tables. Combine this action with n8n's expression syntax to build dynamic queries using data from previous nodes.

The Insert action streamlines adding new records to your CrateDB tables. Instead of constructing raw INSERT statements, you configure the target table and columns, and n8n handles the SQL generation automatically based on your incoming data.

Key parameters:

• Credential to connect with: Required dropdown for selecting your CrateDB authentication credentials.
• Operation: Set to "Insert" to specify this action will add new records.
• Schema: Required text input specifying the database schema (e.g., "doc" which is CrateDB's default schema).
• Table: Required text input for the target table name where records will be inserted.
• Columns: Comma-separated list of column names to populate (e.g., "id,name,description"). The data values come from previous nodes in your workflow.
• Return Fields: Specifies which fields to return after insertion. Use "*" to return all fields, useful for confirming the insert and getting generated values.
• Additional Fields: Optional section for extra properties.

Use cases: Use the Insert action to automatically log webhook events into CrateDB, create new customer records when leads convert in your CRM, or ingest transformed data from ETL pipelines. It pairs perfectly with loops—process an array of items from an API response and insert each one as a separate row.

The Update action allows you to modify existing records in CrateDB based on a unique key. This is essential for keeping your database synchronized with changes happening elsewhere in your tech stack.

Key parameters:

• Credential to connect with: Required dropdown to select your CrateDB account credentials for authentication.
• Operation: Set to "Update" to perform modification operations on existing records.
• Schema: Required text input defining the target schema (typically "doc").
• Table: Required text input specifying which table contains the records to update.
• Update Key: Required text field specifying the column that uniquely identifies records (e.g., "id"). CrateDB uses this to locate which rows to modify.
• Columns: Comma-separated list of columns to update (e.g., "name,description"). Values come from your workflow data.
• Return Fields: Defines which fields are returned post-update. Use "*" to return all fields and verify the changes took effect.
• Additional Fields: Expandable section for optional advanced configurations.

Use cases: The Update action shines for bidirectional syncs—when a contact changes in HubSpot, automatically update their record in CrateDB. It's also perfect for status updates (marking orders as shipped), incrementing counters, or refreshing cached data. Combine with the Execute Query action to first verify a record exists before attempting an update.