Amazon Redshift (opens new window) is a fast and fully managed data warehouse that makes it simple and cost-effective to analyze all your data using standard SQL and your existing Business Intelligence (BI) tools.
# How to connect to Redshift on Workato
The Redshift connector uses basic authentication to authenticate with Redshift.
|Connection name||Give this Redshift connection a unique name that identifies which Redshift instance it is connected to.|
Full JDBC URL of your Redshift instance. Example:|
|Username||Username to connect to Redshift.|
|Password||Password to connect to Redshift.|
|Schema||Name of the schema within the Redshift database you wish to connect to. Defaults to public.|
|Is this app in a private network?||Choose an on-premise agent if your database is running in a network that does not allow direct connection. Before attempting to connect, make sure you have an active on-premise agent. Refer to the On-premise agent guide for more information.|
# Permissions required to connect
At minimum, the database user account must be granted
SELECT permission to the database specified in the connection.
If we are trying to connect to a Redshift instance, using a new database user
workato, the following example queries can be used.
First, create a new user dedicated to integration use cases with Workato.
CREATE USER workato PASSWORD 'password';
The next step is to grant access to
customer table in the schema. In this example, we only wish to grant
GRANT SELECT,INSERT ON TABLE customer TO workato;
Finally, check that this user has the necessary permissions. Run a query to see all grants.
SELECT u.usename, t.schemaname||'.'||t.tablename AS "table", has_table_privilege(u.usename,t.tablename,'select') AS "select", has_table_privilege(u.usename,t.tablename,'insert') AS "insert", has_table_privilege(u.usename,t.tablename,'update') AS "update", has_table_privilege(u.usename,t.tablename,'delete') AS "delete" FROM pg_user u CROSS JOIN pg_tables t WHERE u.usename = 'workato'
This should return the following minimum permission to create a Redshift connection on Workato.
+---------+----------+--------+--------+--------+--------+ | usename | table | select | insert | update | delete | +---------+----------+--------+--------+--------+--------+ | workato | customer | true | true | false | false | +---------+----------+--------+--------+--------+--------+ 2 rows in set (0.26 sec)
# Working with the Redshift connector
# Table and view
The Redshift connector works with all tables and views. These are available in pick lists in each trigger/action or you can provide the exact name.
Select a table/view from pick list
Provide exact table/view name in a text field
In Redshift, unquoted identifiers are case-insensitive. Thus,
SELECT ID FROM USERS
is equivalent to
SELECT ID FROM users
However, quoted identifiers are case-sensitive. Hence,
SELECT ID FROM "USERS"
is NOT equivalent to
SELECT ID FROM "users"
# Single row vs batch of rows
Redshift connector can read or write to your database either as a single row or in batches. When using batch triggers/actions, you have to provide the batch size you wish to work with. The batch size can be any number between 1 and 100, with 100 being the maximum batch size.
Batch trigger inputs
Besides the difference in input fields, there is also a difference between the outputs of these 2 types of operations. A trigger that processes rows one at a time will have an output datatree that allows you to map data from that single row.
Single row output
However, a trigger that processes rows in batches will output them as an array of rows. The Rows datapill indicates that the output is a list containing data for each row in that batch.
Batch trigger output
As a result, the output of batch triggers/actions needs to be handled differently. This recipe (opens new window) uses a batch trigger for new rows in the
users table. The output of the trigger is used in a Salesforce bulk update action that requires mapping the Rows datapill into the source list.
Using batch trigger output
# WHERE condition
This input field is used to filter and identify rows to perform an action on. It is used in multiple triggers and actions in the following ways:
- filter rows to be picked up in triggers
- filter rows in Select rows action
- filter rows to be deleted in Delete rows action
This clause will be used as a
WHERE statement in each request. This should follow basic SQL syntax. Refer to this Redshift documentation (opens new window) for a full list of rules for writing Redshift SQL statements.
Greater than |
Greater than or equal to
Less than |
Less than or equal to
|IN(...)||List of values|
|LIKE||Pattern matching with wildcard characters ( |
|BETWEEN||Retrieve values with a range|
IS NULL |
IS NOT NULL
NULL values check |
Non-NULL values check
# Simple statements
String values must be enclosed in single quotes (
'') and columns used must exist in the table.
WHERE condition to filter rows based on values in a single column looks like this.
currency = 'USD'
If used in a Select rows action, this
WHERE condition will return all rows that have the value 'USD' in the
currency column. Just remember to wrap datapills with single quotes in your inputs.
Using datapills in
Column names with spaces must be enclosed in double quotes (
""). For example, currency code must to enclosed in brackets to be used as an identifier. Note that all quoted identifiers are case-sensitive.
"currency code" = 'USD'
In a recipe, remember to use the appropriate quotes for each value/identifier.
WHERE condition with enclosed identifier
# Complex statements
WHERE condition can also contain subqueries. The following query can be used on the
id in (select user_id from tickets where priority = 2)
When used in a Delete rows action, this will delete all rows in the
invoices table where at least one associated row in the
accounts table has a value of 2 in the
Using datapills in
WHERE condition with subquery
# Unique key
In all triggers and some actions, this is a required input. Values from this selected column are used to uniquely identify rows in the selected table.
As such, the values in the selected column must be unique. Typically, this column is the primary key of the table (for example,
When used in a trigger, this column must be incremental. This constraint is required because the trigger uses values from this column to look for new rows. In each poll, the trigger queries for rows with a unique key value greater than the previous greatest value.
Let's use a simple example to illustrate this behavior. We have a New row trigger that processed rows from a table. The unique key configured for this trigger is
ID. The last row processed has
100 as it's
ID value. In the next poll, the trigger will use
ID >= 101 as the condition to look for new rows.
Performance of a trigger can be improved if the column selected to be used as the unique key is indexed.
# Sort column
This is required for New/updated row triggers. Values in this selected column are used to identify updated rows.
When a row is updated, the Unique key value remains the same. However, it should have it's Sort column updated to reflect the last updated time. Following this logic, Workato keeps track of values in this column together with values in the selected Unique key column. When a change in the Sort column value is observed, an updated row event will be recorded and processed by the trigger.
Let's use a simple example to illustrate this behavior. We have a New/updated row trigger that processed rows from a table. The Unique key and Sort column configured for this trigger is
UPDATED_AT respectively. The last row processed by the trigger has
ID value of
UPDATED_AT value of
2018-05-09 16:00:00.000000. In the next poll, the trigger will query for new rows that satisfy either of the 2 conditions:
UPDATED_AT > '2018-05-09 16:00:00.000000'
ID > 100 AND UPDATED_AT = '2018-05-09 16:00:00.000000'
For Redshift, only timestamp and timestamptz column types can be used.