SyncSpider recognizes and has a few different fields types like Constant value field, Custom field, Complex field, and Option field.
In this example, on how to send the customer order details from ThriveCart toMooSend mailing list, you will see the use of all different field types mentioned.
And we believe that if you follow this example, you will easily understand all the differences among these fields.
Here is a full video about the mention use case it self. Step by step instruction below, with explanation on detailed field is below.
We will start this integration by creating a task.
First step is to connect ThirveCart and MooSend integration modules with SyncSpider.
Then, we can move on to Creating e a new task. Go to the Company/Project where you want to Create a new Task and click on the upper right side of the screen.
Then, we are gonna use ThriveCart as a Source and MooSend as a target destination.
Then click Next.
As ThriveCart uses webhooks for integration, it will display the URL as shown. Copy the URL and paste to ThriveCart and click Next.
In our help file on How to integrate ThriveCart you will see all instruction where to paste that code.
Note: Next step will give you the option to filter destination data (in this case ThriveCart order data) if you want. We are skipping this step in this tutorial.
Finally, we are at the mapping screen, and this is where you will understand the different fields SyncSpider supports.
Constant Value & Options & Complex fields
The first field is the "Mailing List" which is the OPTIONS field. Every option field has multiple values that could be selected.
In the mapping screen, left side always represents the Source, while left is the Target. Meaning that on the right we are seeing an Options field from MooSend.
We need to drag Custom value field to map it with Options field ( in this example, Mail list field).
Constant value field is there so you can set a constant value to any Options field.
As as soon as you drag the Constant value field to any Option field ( in this case Mail List field), all possible options you have for that Option field will appear.
In this case, this means that you can select any Mailing List you have in your MooSend account and set it as constant for this task.
In my example, as shown below, I have selected my Monobunt mailing list. Additionally, I have mapped the rest of the fields as you can see below.
Note that I We can pulled out Email and Name values from ThriveCart COMPLEX field "Customer".
Complex fields are noting more than field that contain a collection of attributes in them.
It is important that SyncSpider can read different Complex fields and t give you the option to select what exact attributes (data) you need from such field.
This way, you can simply select that you need (e.g. Email and Name fields form Complex field Customer) from that Field - you don't have to pull in everything.
Using Custom, Group & Complex fields
Custom fields are essential to build an exact task or workflow you need.
We can also add custom fields if SyncSpider if we want. SyncSpider can read custom fields in most of it's integration modules.
Custom fields are always need to be generated in Target destination system first.
E.G. In ThriveCart you may find many different attribute fields you need to put to your MooSend list. But, these attributes fields may not exist in MooSend. That's why SyncSpider can read Custom Fields in most of our integration Modules.
Let us now add a Custom field to MooSend and see how we can use them in SyncSpider.
Go to your MooSend account click on view lists🡪 select the mailing list🡪‘add new custom field’ and enter the details like shown here and save it.
Here, we are adding the Order field.
Now, let us get back to SyncSpider. Here, in MooSend example, you can see that we have multiple different Custom fields to map.
You will notice that we don't see the Custom "Order" field we just created. That is because SyncSpider can't dynamically read Custom data from Target system.
That's why, we have introduced these Group and Option fields.
Note that Option field has noting to do with OptionS field!
Group field represents the Custom field. Is the field that you need to map with Constant value field, and then tell SyncSpider which Custom field within SyncSpider you want to target.
Let us now drag the Constant value field to Group1, and name it Order - like the Custom field we just created in MooSend.
Note: The name we put in Constant value field has to be the same as created in Target system (caps sensitive), otherwise SyncSpider will not send the data you need to proper Custom field in your Target system.
Every Group field has it's Option field.
Option field is for the data/attribute you want to send to the selected Custom field.
E.G. We want to send "Total" attribute from ThriveCart to MooSend Custom field "Order".
To do so, first we need to tell SyncSpider what is the Custom field Group1 represents. We do so by mapping the Constant value field with Group1 field and naming it exactly as we named the Custom field in MooSend.
Then, we simply map the desired attribute from ThriveCart, "Total", with Option1 field.
You can do this for X number of different Custom attributes.
I hope this more clearer now. This is the way we are trying to give you as much flexibility for your automation.
Let us know if you need more clarifications.
This is just of the integrations offered by SyncSpider.
To check the list of the tools and features we support, please click here.
If you don't see your favorite tool on our list, please take the time and send us a request here to create an integration for you OR Up-vote it if it's already on the list :)
We develop the integrations based on the requests and up-votes :)
If you got any questions or need assistance, feel free to contact our support team via the chat widget on our site and within SyncSpider app.