How long does it take to set up Tarsal?

It depends on your source and destination. Configuration is as easy as filling out a form, and the leg work simply comes down to gathering the appropriate prerequisites for setup. This may include authentication information, ARNs or Database connection information. You can view the prerequisites in our Sources and Destinations pages.

Do you store my data?

Date is transiently stored in our system while it's waiting for processing or delivery. Once delivered to the destination, the data is purged. This interstitial storage is in place to make sure your data is delivered successfully, even if the downstream destination is unavailable.

What happens if a Tarsal flow fails?

Data is not lost when a flow fails, however no data will be added or updated in your destination. You can set up notifications about your failed flow so that you can begin troubleshooting.

  • We update the flow status in your Tarsal dashboard to "failed."
  • If you have notifications enabled on your account, we send you a notification.

Once you resolve the issues that caused your flow to fail, Tarsal automatically resumes your flow from where it left off.

Tarsal has relationships with vendors to stay up to date of API changes. However, in the event a flow fails because of an unannounced vendor API change, Tarsal is also notified and will research and make the appropriate changes. Once the updates are deployed, the system will pick up where it left off. No intervention is needed on your end.

Does my data change?

Many sources provider their data in JSON format. A disadvantage of JSON is that it does not natively support value types of float or integer - both are provided as a type number. In these cases, Tarsal may modify the value type to be one of integer or float instead of number. If this is the case, you will see a Data Type Mappings table in the documentation.

Data Type Mappings

Integration TypeTarsal Type