Integrating with other systems
How to connect Tepez to a CRM, an ERP or any other system, and what to send us when you need a custom integration.
Tepez has no built-in connectors to other business systems: none for Priority, SAP, Hilan, DocuSign or any other product. You connect Tepez to another system with the API and with the form's own email rules, from your code or from an automation platform such as Make or Zapier. This page shows which building block fits which need, and what to send us when none of them does. For your IT team's questions about how the connection is secured, see Security.
The building blocks
| You want to | Use |
|---|---|
| Send each submission to another system as it arrives | An email rule to a Make or Zapier inbound address, which then calls the other system. See Get notified when a form is submitted. |
| Copy entries into another system on a schedule | Poll GET /entry for entries that changed. See Poll for changes. |
| Load a file into a system that imports CSV or Excel | Export the entries to CSV or Excel, and convert the file to that system's format. |
| Open a form with data from another system | Prefill the form from a link, or create a personal entry through the API. |
| Record data from another system as a submitted form | Submit entries from your server. |
| Keep the signed PDF in another system | Read archivedRenders from the entry. See Files and PDFs. |
Make and Zapier
Make and Zapier connect to thousands of systems, and they work with Tepez through two generic modules, without a Tepez app:
- An inbound email starts the scenario (a Zap, in Zapier) when a form's email rule sends it a submission.
- An HTTP request calls the Tepez API with your key, for example to read the whole entry or to submit one.
Between the two, the platform's own modules for the other system do the rest: create a record in a CRM, add a row to a sheet, upload the PDF to storage. Recipe 1 builds such a scenario step by step.
When you need a custom integration
Some systems need more than these building blocks, for example a system that accepts data only in its own file format or through its own API. Tell us about it, and we'll reply with what fits: a recipe with the building blocks above, or what a custom integration would take.
Send us:
- The system: its name, and a link to its API documentation if it has one.
- The direction: data from Tepez to the system, from the system to Tepez, or both.
- How it authenticates: an API key, a username and password, OAuth, or a file you upload by hand.
- The request it expects: the URL, the method and an example body, or an example file.
- The volume: how many entries a day or a month, and how soon after each submission the data must arrive.
Question about this page? Email support@tepez.co.il