With over 1000 pre-built connectors, the Jeto Workato Connector allows you to integrate Jeto and campaign data with your entire stack.
Here is what you will need to activate it for your account and start putting data together and start integrate your stack and automate your work even further.
You must be part of the Jeto API Beta program to access this Connector. See Jeto API Integrations (Beta) for details.
Once registered for the program our team will securely share your API user credentials.
Access to connector here.
Select "Install Connector".
Add the connector to your recipes
Once installed, the Connector will become available from your recipe editor.
To create a Jeto Connection:
Add a new API user to your Jeto Account with the following configurations
First Name: Workato (or chose your own name)
Last Name: Connector (or chose your own name)
Email: Any valid email of your choice (you will need to have access to this inbox)
Optional - add the new user to an "API" group where you will share launchers & campaigns visible to the API
Activate this user (via the email in your inbox)
Select and share the Launcher(s) you want to use with the Connector.
In Workato Create the new connection. Select Jeto App and enter your users credentials as well as the Client ID and Client Secret previously shared with you.
Use the connector in recipes
You can now build recipes using prebuilt triggers and actions. Here is what we've made available for you.
New Campaign: trigger a recipe each time a new campaign is created.
Updated Campaign: trigger a recipe each time a campaign is updated.
Create New Jeto Campaign
Create a new Jeto Campaign using the following parameters:
Launcher ID: Type the ID of the Launcher you wish to use for this campaign. The ID can be found in the Jeto Launcher's URL path of your Jeto Launcher. Ex: https://app.jeto.io/launchers/XXXXXX/edit;
Chose "campaigns" to create a Campaign or campaignDrafts to create a draft;
Attributes/Form/Form field: use the Jeto field key / Marketo token name
Value: enter a value for the related campaign field or use a "pill" from a previous step.
Returns all campaigns accessible to your user. It supports Filter, Sort, Search and Paging.
Get Campaign Details
Retrieve the campaign form data associated to an existing campaign, including each campaign field and its corresponding value.
Campaign ID: ID or UUID of the campaign. This ID can be found in the Jeto Campaign's URL path. Ex: https://app.jeto.io/campaigns/XXXXX/edit or use a pill from a prior step (Ex: Get Campaigns);
Get eligible Jeto Campaign Owners
Returns a list of users eligible for transfer of campaign ownership (to use in conjunction with Change Jeto Campaign Owner below).
Launcher ID: Set a value for the Launcher ID.
Update a Jeto Campaign
Campaign ID: Use the pick-list to select from an existing campaign to update;
Form / Field: Set a value for each campaign field
Optionally you can set additional Data Attributes:
"Email modules": ID's of email modules to delete by setting "Is Deleted" = 1
"Lp variables": ID's landing page modules to delete by setting "variable value" = "false"
"Owner ID": update campaign owner by setting user ID (see Get eligible Jeto Campaign Owners to obtain the list of eligible owners.
Change Jeto Campaign Owner
New Owner ID*: Set the identity of the new campaign owner.
Custom actions are a great way to implement a "Catch All" for any API call that does not have a predefined action. Take note that all requests sent from your custom action will inherit your authorization details like tokens as well as authorization logic for token refresh. Please refer to The Ultimate Guide to Custom Actions in Workato for additional help on using custom actions.
Limitations and Future Improvements
Get Campaign Details partial response on fast Create + Get consecutive transactions. If you create a campaign via the API and immediately request the related campaign details, you may receive only partial results due to the relative timing of the query.
Workaround: simply add a wait steps between these to actions, we recommend a minimal wait of 30 seconds.
Fix: We'll fix this issue by delaying our response until the object is fully created.