Step 1: Becoming a Tonkey 101

Goals

To plan out an onboarding and training plan for new users to Tonkean. To have an environment ready to deploy to each customer to “fill in” but also get certified.

Tonkey Level 1

• Create and Deploy Modules

• Add a Data and Communication Components

• Create a basic flow

• Assign themselves on Live Report

• Invite another email and set as maker

In this level 1 certification, we are going to do a broad overview and implementation of basic Tonkean components. By the end of this you should have connected an email enterprise component as well as used the inbox to copy the message to another email or communications tool message.

Certification and walkthrough

Module pre-work: None, all these will be components that can be generated through the walkthrough

Training and verification steps:

1. Create an Enterprise Component for Email Inbox and name it “Intake Box”, you’ll have to click +Add Data Source, Email Inbox, and make sure that you specify which Solutions have access by going into the data source and clicking on “Solution Access” and pointing to the Solution, or the folder that has all your future ops modules in your Solution Studio’s page

2. If you go to “Connections” within the Intake Box, click on Edit and you’ll see an Inbox address generated. You can go ahead and copy and paste the email generated and send an email to this data source, this can be populated with any text so that you’re able to see the preview in the data later (nothing will happen yet)

3. (Optional) Connect a Communications Source for one of the options, if Slack or MS-Teams is not available, then we will use Email later, this is under the sub tab in Enterprise Components

4. In Solutions Studio, Create a new Module, Name it Email to Notification

5. Under “Start here” and click on the the Intake Box (Email Inbox), your emails wil now flow into this entry point, but we’ll need some fields

6. Add relevant email fields from Fields menu 

   • (Click on the “Fields” button , add Subject (clean), Body, From (email), Recipients)

7. Add a “Send Notification” action after the Item is Added trigger

   • Click on the + icon after the “Item is Added” (the lightning bolt signals a trigger), Look for Send Notification (Note, Ask a Question is a similar action block, but it enables you to add buttons for decisions, you can play with this later)

8. Reply back to the Email that came in with the Email Message

   • In Send Notification, select the notification method, and enter your email in the “Email from field” (or use the From (Email) field)

   • If Email, enter anything for subject

   • For rest, for the message body, type in “New Email from: “ then add the From field with the Insert field sign. Then type in “Message body: “ and add the Message Body field

9. Create a new Match Condition to route a subject “hello” differently

   • To the left of the “Item is Added” trigger, click the , and select “Match Condition”, this will create a new conditional trigger

   • On the right side, click on the Add new condition, select the “Subject” field

   • Click on the condition field, select condition “contains” and type in hello)

10. Click on your original Send Notification, the menu drop down has a “Duplicate”, click this to reuse it

11. Drag this to the Match Condition below, turn it on with the top right, then change the Email Subject to, “This message said hello”. You’ve now set two different notifications for different conditions!

12. While you’re here, you can turn on your module by clicking on BUILD -> PRODUCTION, and turn on the module after publish

Deploy the module

1. Click on “Mark for Publish”, it will pop up a few test pages, but just click Next and Continue until you get to a “Describe your change”, you can type in “First Draft” for this and click Mark for Publish

2. Return to the Solutions Studio page, click on “Publish Version”

3. If there are other modules waiting to be published, mark them as ready or revert them to go to last version (warning, revert will wipe modules that were never published!)

4. Click on Publish and fill out the notes. 

Send your first Email and test this module

1. Make sure to grab your email address

   1. As a reminder,  it’s in Enterprise Components -> Intake Box -> Connections -> Edit, and you can Copy it

   2. A good practice is to add it to an alias or a group so you don’t have to memorize it for future email projects

2. Send 2 emails to this address, make sure to put “hello” in the subject in one of the emails and not in the other

3. Click on View Data and check if they popped up

4. Check your messaging notification source and see if the right notifications came in!

Checking business reports

Business reports are a way to monitor each transaction that starts in your module, the “History” is where you can monitor the transaction in each block, and finally the “Runtime” function can monitor transactions across your entire set of workflows

Here we’ll just touch base on Business Reports, where you can pull in fields and check status on items if you want to update them in the flow

 

1. Check if emails came to live report

2. If you’re in build mode, you can add more fields, add Emails - Body, Emails - Subject (Plain), and Emails - From (Email)

3. You’ll need to republish and deploy the changes, but your Business Report will now have greater visibility with what’s happening to your workflow

As reference, is in the module top right corner, and Runtime is in the top left main menus:

 

You are now a Tonkey Level 1