You may use following properties to configure a connection:
other types of configuration parameters are also supported, more information and samples you can find here
With this action you may fetch data out of the database, e.g. using
This trigger & action has no limitations on the number of rows so you may expect to get all of these
via sequential fetching that is implemented within the node.js
Component will remember last execution timestamp and let you build queries on it:
select * from Leads where Created >= '%%EIO_LAST_POLL%%'
where just before executing the statement the
%%EIO_LAST_POLL%% will be replaced with ISO Date of the last execution, for example
2017-08-25T07:43:48.127Z. During the first execution, date will be equal to the bigging of time -
Check the SELECT Action description above.
You may use this action to do the operations that are not producing output rows but do the database manipulations,
DELETE statements. Internally we use prepared statements, so all incoming data is
therefore when doing a prepared statements you would need to add
:type to each prepared statement variable.
For example if you have a following SQL statement:
INSERT INTO Test2.dbo.Tweets (Lang, "Text", id, CreatedAt, Username, ScreenName) VALUES (@lang, @text, @id, @created_at, @username, @screenname)
you should add
:type to each
@parameter so your SQL query will looks like this:
INSERT INTO Test2.dbo.Tweets (Lang, "Text", id, CreatedAt, Username, ScreenName) VALUES (@lang, @text, @id:bigint, @created_at:date, @username, @screenname)
Following types are supported:
string(also default type if type is omitted)
number(will be converted to MSSQL
boolean(will be converted to MSSQL
date(will be converted to
more details can be found here
Component supports dynamic incoming metadata - as soon as your query is in place it will be parsed and incoming metadata will be generated accordingly.
No known issues are there yet.