Connector with Snowflake

Hi all,

I try to import from Snowflake database to create records in a Tulip table.
We managed with my IT guy to set the Snowflake connector and to get the data in the Tulip environment.
What I don’t understand now is how to use this connector to creat records in a Tulip table ?

For example on the picture below I would like to use :
data.0.0 which is my Product ID
data.0.4 which is my Product Name
data.0.9 which is the Order Date
And create a record in my tulip table with these data.

Thanks a lot for you help !

Hi Paul,

To transfer results from a connector into a Tulip table, you can use triggers within your Tulip app. First, create a trigger to call the connector function, then store the connector’s output into a variable. From there, use another action within the same or a subsequent trigger to write the variable’s value into the appropriate fields in your Tulip table.

For example, once the connector pulls the data, store it in an array or object, and map each field in that array to a corresponding column/field in your table using “Store” actions within your trigger setup​

This article should be helpful as well! How to Call a Connector Function using Triggers

Hi Beth,

Thanks for your inputs !
Is there a way to do this in the Automation ? I saw that you can run a connector from the Automation system. Is it possible to save the Outputs of the connector into a table with the Automation system ?

Thanks,
Paul

Yes, this can also be done with Automations!

You could use a scheduled event and trigger the automation with it. Then run the connector function from the automation and use the output to create a record in another action. This will require looping ion the Automation as well, to create a different record each time, based on the length of the array.

Note: Depending on the amount of records and data to be created, you may hit the 60 seconds limit timeout. So you should be proactive in the amount of records created. An option is to split them in 100 records at a time (or even less, depending on how much data you are passing in the connector, which here looks like a decent amount).

You can also see a creative solution to this timeout in this post from @steve.midcalf Using Looping in Automations to move 450 records from Staging Table to Production Table