CALL-E and Tiliter Integration
Keep CALL-E and Tiliter matched by integrating their events and actions. When ai events happen in CALL-E, update the Tiliter automatically - without any line of code in visual workflow builder.
- 3-day trial
- Cancel anytime
- Up to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about CALL-E and Tiliter
Detailed info you need to know about CALL-E and Tiliter integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect CALL-E to Tiliter
Set up your CALL-E and Tiliter integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.
STEP 1
Connect CALL-E and Tiliter
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow[3]. No coding or API skills required.
STEP 2
Build a workflow
Paste selected CALL-E and Tiliter nodes onto the canvas[4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between CALL-E and Tiliter. Use filters or a JS custom code step in between. Everything is on the canvas.
How does the integration between CALL-E and Tiliter work in WEXTL?
WEXTL exposes actions and triggers for CALL-E and Tiliter that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.
CALL-E triggersTiliter actions
CALL-E modules
- Cancel a Call Stops a call that has not been handed to the telephone provider yet. Once dialing has started the call cannot be hung up, and a call that already finished is returned unchanged.
- Create a Call Places an AI phone call to a Phone number that carries out a Task and collects the answers described by your Result Fields. Add a Webhook URL to be notified when the call ends, and Metadata for your own labels.
- Create a Goal Run Starts a call to a Phone number for one goal, filled in with Variables sent as text, numbers or Yes or No values. The call runs in the background, so use Get a Goal Run to read its Result later.
- Get a Call Reads the saved state of one call by its Call ID, with the Status, Result and Transcript. Reading never dials, and the same call may be read repeatedly while its Result Status says pending.
- Get a Goal Returns one goal from your account, including the schemas in its Published Run Spec. Look at them before Create a Goal Run to see which Variables a call expects.
- Get a Goal Run Checks how a goal run is going, using the Goal Run ID from Create a Goal Run. It returns the Call Outcome, the Result and the Transcript. Run it again until the Result Status is no longer pending.
- List Call Events Lists what happened during a call, from accepted through ringing and connected to completed, oldest first. A Starting Cursor continues a list you read earlier, and every event is one row you can map.
- List Goals Shows the goals published in your CALL-E account, with the Title, Description, Status and Published Run Spec of each. Use Limit to cap how many are returned.
- Make an API Call Makes an authorized free-form request to the CALL-E REST API with your saved credential.
- Watch Call Completed Starts the workflow the moment CALL-E delivers a finished call, whether it completed, failed or was canceled. It runs instantly through a webhook, so the address of this node is pasted into the call you create.
Tiliter modules
- Create a Product Adds a retailer product to Tiliter from its Product ID, Product Name, Department, Unit Price and Currency. Use Sale Method to sell it by quantity or by weight, and Lookup Code to store a PLU or UPC for it.
- Create a Selection Report Reports which product a shopper ended up choosing after a recognition, using the Recognition ID and the Selected Product ID. Set Selection Method to Automatic or Manual, and add a Transaction ID to tie it to your own sale.
- Create a Transaction Event Logs a step in a transaction against a recognition, such as Purchased, Label Printed or Transaction Cancelled. Choose it with Type, set the Time it happened, and add a Detail note or Meta Data pairs.
- Delete a Product Deletes a catalog product in Tiliter.
- Delete a Store Deletes a store from the list of stores in Tiliter.
- Get a Product Loads one product from the catalog, with its Product Name, Department, Sale Method, Lookup Code and Image URL.
- Get a Store Reads a single store and returns its Friendly name, Region, Country and Area code.
- Get Store Stock Data Reads the stock data kept for one store, which is a list of Product stock states.
- List Products Fetches the products in your Tiliter catalog, with the Product ID, Product name and Department of each. Use Limit to cap how many are returned.
- List Stores Fetches the stores on your account, with the Store ID, Friendly name and Country of each. Use Limit to set the most results returned.
- Make an API Call Calls the Tiliter REST API directly with a free-form request under your saved credential.
- Recognize a Product Sends one or two Images from a Device ID to Tiliter for recognition of the product in them. Turn on Include Scores to add confidence scores, and use Max Options to limit the options offered. Returns a Product recognition and a Bag recognition.
- Update a Product Changes an existing catalog product and always sends its Sale Method. Update the Product Name, Unit Price, Department or Image URL, and turn off Recognition Enabled to have Tiliter ignore the product.
- Update Store Stock Data Sets the Stock States held for one store in Tiliter. Returns the updated Product stock states.
Explore alternative integrations
There are other apps[9] supported by WEXTL that can be paired with CALL-E and Tiliter integrations. Pick any from the list below if the current combination isn't the one you need.
Frequently asked questions
Common questions about connecting CALL-E and Tiliter.
References
List of sources used to gather information about the CALL-E and Tiliter integration.
- CALL-E and Tiliter integration source code, module specs and credentials implementation.
- Our CALL-E and Tiliter integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for CALL-E and Tiliter, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- CALL-E integration information
- Tiliter integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library
How we write our apps documentation
Explore how WEXTL® crafted CALL-E and Tiliter integration page documentation. Used sources, the role of AI, and how the team validates the result.

