Category Archives: Product Updates

Zendesk Decision Tree Support App: Version 4

zendesk_zingtree-BLOG@2x

Travis A., who is implementing Zingtree for a video technology company, was keen on using Zingtree to try to reduce his team’s support ticket load. He also needed to import a synopsis of the Zingtree session data into his Zendesk tickets so his tech support people could get some time-saving background information.

Travis wanted to emphasize the condensed Q&A part of the session. Done!

Here’s the new look of the Zendesk Decision Tree Support app:

Here’s what’s new in the Zendesk Support App, version 4:

  • The Q&A view is now the default.
  • Any “back” or “restart” button clicks no longer show in Q&A view.
  • The answers clicked are highlighted, so it’s easy for a support person to see where the customer went at a glance.

You can download the latest Zingtree Decision Tree Support app for Zendesk here.

Need help installing the app? Instructions are here.

Travis' photo
This is Travis.

Thank you, Travis, for the awesome suggestions!

Spring 2017 Decision Tree Updates

updates-blog2

In case you haven’t noticed, we’ve been busy improving Zingtree over the past six weeks. Aside from the new Single Sign-on and Dual use tree features, here are the other more subtle updates we’ve recently added into Zingtree:

  • Fix: No longer allows multiple feedback clicks on submit feedback button (Katheryn P.).
  • Update: AGENT_ and USER_ prefixes on buttons only show them in agent mode or end-user mode (Travis A.).
  • Update: Tag matching on trees (host-trees) now saves state for each tree clicked, shows marker if a session was started with that tree (for Jenn V.).
  • Update: Added nochrome=1 option to host-trees to show minimal tag matching results.
  • Fix: Using a tree node to launch a tree with a webhook in the starting node now runs webhook (Chrissie).
  • Update: Reports are now in author’s local time.
  • Update: Zendesk app version V9B now manages merge variables properly.
  • Update: Zendesk app gets ticket’s list box values instead of tags as merge variables to insert into agent scripts.
  • Fix: Form data report items now syncs with session list report (Diana T).
  • Fix: Session Matrix report now uses last click time for date ranges.
  • Fix: Scoring nodes no longer occasionally add a zero to scoring variables.
  • Fix: email-session-info script updated to handle some timing issues causing missing form data.
  • Update: Data Entry radio button fields now render using entire width of node, not half of width.
  • Fix: Date picker for subtrees works properly (Chrissie).
  • New: Sessions List has options to show first click/last click (Ricardo).
  • New: Sessions list report shows total time spent.
  • Update: Added Agent Portal Parameters option to pass custom URL values into agent portal trees (Chrissie).
  • Update: My Agents page now hides advanced options by default.
  • New: Server-side include example page.
  • Fix: Last click time in session data now always accurate (Ricardo).
  • Fix: Session form data reloads are now more reliable – fixes edge cases on timing errors (Ricardo).
  • Fix: New lines in Agent Feedback Comments now appear in emails, comment review pages (Katheryn P).
  • New: Tree Nodes and Link Nodes can now have tags (Morgan).
  • New: find_tree_sessions API (Chris P.).
  • Fix: Double quotes in session variables (via Zendesk) caused state not to get properly set (Ricardo).
  • New: API added find_agent_sessions as equivalent to original find_sessions. Makes better language since we added new find_tree_sessions API.
  • Update: get_session_data API call now includes “seq” in the path as click number (Chris P.).
  • Update: Form data, Session List reports now based off of “last click time” during a session, instead of start time (Ricardo).
  • Update: Session List report now shows an icon if the session includes form data.
  • Added demo for embedding with breadcrumbs in the container.
  • New: Import from Oracle Service Cloud XML in Create Tree.
  • Fix: FontAwesome icons updated to version 4.7 for Preview, Deploy.
  • Fix: FormData report and Session List report now use same time starting criterion.
  • Update: Added date_format option to hosting or embedded URLs to allow custom date formats in date picker (Chrissie, Jane).
  • Fix: Properly sends ampersands in subject line for email-session-info link node (Alok).
  • New: Can now see all feedback comments for a tree by clicking on comments bubble in My Trees (Guil).
  • Update: Date picker now uses user’s locale to format dates and show proper month names.
  • Fix: Emails with apostrophes now are able to be added to MailChimp lists.
  • Fix: Validates Tree IDs on spreadsheet import for tree nodes.
  • Fix: Now gets root node for tree imports as first node in list, even if not #1 (Katie).
  • Update: Zendesk agent scripting: tags prefixed with “perm_” are never removed from Zendesk once added (Jamel).

Thanks to all of our hard-core authors for suggesting most of these updates.

Got a suggestion or a great idea?  Let us know!

Single Sign-On for Zingtree Decision Trees

security-blog

We’ve had several requests to incorporate Single Sign-on (SSO) into Zingtree, as a means of restricting access to trees.  Many customers have sensitive corporate processes or procedures encapsulated in their trees, and ensuring these trees are accessible only to certain employees can be invaluable.

Single Sign-on is a service provided by many vendors, including Okta, Microsoft (Active Directory / Azure), Google (G-Suite), Salesforce and more.  These services are known as Identity Providers.  A single log-in through an Identity Provider gives a user secure, authenticated access to applications provided by Service Providers like Zingtree.

Once you log in through your Identity Provider, you don’t need to re-enter your login credentials. SSO is a very convenient way to secure access to your applications, while not burdening end-users with extra hurdles.

Zingtree supports any service that is SAML 2.0 compliant, which is a common standard.

Set Up Overview

Configuring SSO requires your Identity Provider and Zingtree to share information with each other:

  1. Your Identity Provider needs information about Zingtree.
  2. Zingtree needs information about your Identity Provider.

SSO just needs to be set up once for your organization. Once you have Zingtree and your Identity Provider successfully working together, you can mark any of your trees as “SSO restricted” via the Settings tool to require a login to get access.

Configuring Zingtree for SSO

To start, in the Zingtree top menu, go to Account, Single-Sign-on. You’ll see the parameters (specific to your organization) to share with your Identity Provider:

Configure your Identity Provider with these parameters.

Next, click the blue button to Enter Identity Provider Data into Zingtree. The following screen appears:

Copy the rest of these settings from your Identity Provider.

If you’re ready to test, make sure Enable access restrictions on specified trees is checked.

Click Save Identity Provider Settings when finished.

Testing Your SSO Setup

Once you’ve set up your Identity Provider and Zingtree for SSO, you can test from Zingtree as follows:

  1. In Zingtree, go to Account, Single Sign-on.
  2. Click the orange Test Setup button at the lower right of the page.

From here. you can test logging into your Identity Provider from Zingtree.  If you’re already logged in, the test will just return your email or other identifier from your Identity Provider.  If you’re not yet logged in, the Identity Provider’s login screen will appear, and then you will be returned to the Zingtree SSO test page after logging in.

Enabling SSO on Your Trees

Once SSO is working properly from your test, you can restrict access to any tree as follows:

  1. Go to My Trees, and select the tree that you want to require SSO login.
  2. Click the Settings tool.
  3. Check Require Single Sign-on (SSO) Login to Access.
  4. Click Update Settings.

Release Notes

SSO has been tested with a variety of Identity Providers.  If you’re having trouble configuring with a specific service, please let us know!

How To Use One Tree for End-Users and Employees/Agents

updates-blog

We’ve had requests to make it easy to use one tree for both end-user support and internal agent usage. Rather than maintaining two separate trees, being able to have one source of content and show (or hide) parts between agents and end-users can be extremely helpful. So, we’ve introduced two new template tags that allow this to happen.

Demo

The Dual Use Agent and End-User Example Tree from the Zingtree Gallery shows how this type of tree is built and operated. You can switch between End-User and Agent views by opening the Show More Display Options link.

Creating Agent-Only or End-User Only Buttons

The first node in the demo has a button labelled “Other Options for Agents only”.  This button only appears when agents are viewing the tree, but not for end-users.  Here’s how this magic is done:

  • If you prefix the button label with AGENT_ , only agents will see that button.
  • Prefix a button with USER_ to show it to just end-users.

Creating Nodes with Dual Content

In the content area for any node, you can insert special tags that make the text visible to just agents, or just end-users.

To show content for agents only:

Surround the content with [[AGENT-ONLY]] and [[/AGENT-ONLY]].

To show content for end-users only:

Surround the content with [[USER-ONLY]] and [[/USER-ONLY]].

You can access these template tags from the content editor in any node:


Example

If your node content area looks like this…

This is the content for a node.

[[AGENT-ONLY]]Agent stuff shows here[[/AGENT-ONLY]]

[[USER-ONLY]]User content shows here[[/USER-ONLY]]

An end user will see this…

This is the content for a node.

User content shows here

And your agents will see this…

This is the content for a node.

Agent stuff shows here

How to Preview

The updated Preview tool lets you see content views for agents or end-users:

Implementation

Your agent-only content will appear in trees accessed via the Zingtree Agent Portal. You can also make this content appear by adding the following parameters to the URL for Zingtree hosted or embedded trees:

&agent_mode=1&apikey=YOUR_API_KEY

Substitute your API key for YOUR_API_KEY in the URL. You can find the API Key from the API page, or if you have multiple organizations at the bottom of the Organizations and Billing page.


Do you like this new feature? Or have any other comments? Please share with us!

Updates: Spreadsheet Import Enhancements and More

updates-blog

When we launched our new feature that allows you to create decision trees from Excel and Google Sheets, we had no idea this feature would be as popular as it has become. Some of our bigger clients, in particular, have really run with this and suggested a lot of great improvements.

Here’s what’s new with spreadsheet decision tree imports:

  • Fix: Validates Tree IDs on spreadsheet import for tree nodes.
  • Fix: Importing and replacing a tree keeps the tree’s settings intact (Elliott).
  • Update: Spreadsheet import allows columns in any order (Elliott).
  • Update: Spreadsheet import allows for a Tags column (Jamel).
  • Fix: Errors in spreadsheet import won’t delete a previous tree if we’re replacing a tree.
  • Fix: Importing Excel with line breaks in cells now works properly, retains line breaks (Charlie).
  • Fix: Importing pasted spreadsheet data now saves the first iteration in Snapshots tool.
  • Update: Spreadsheet import can now include TREE and LINK nodes (Elliott).
  • Update: Exporting CSV tree from Overview/Simple now adds TREE and LINK node types into CSV data.
  • Fix: Importing trees with button links to non-existent nodes now sets the link to “unlinked” (Elliott).

We’ve also done some other tweaks outside of spreadsheet imports:

  • Update: Use “send_zendesk_button” as a node tag to send the button text to Zendesk as a tag instead. (Elliott)
  • Fix: Agent Portal now shows merge variables for agent_name (Craig).
  • Update: Added Agent List export to the My Agents page (Gene).
  • Update: Added more error checks to Add Multiple Agents input tool.
  • Update: Made show/hide tree name option more visible in iFrame Advanced Options.
  • Fix: Copying a Gallery tree into a new account works properly.
  • Update: Max attachment size in email nodes increased to 25 Mb (Dan B.).
  • Update: Merge variables now has an option to retain plus characters (Chris).
  • New: API call to delete session data from our servers for a particular session ID (Jay).
  • Fix: email-session-info occasionally failed when data was entered right before sending (Alok, Craig).

Phew!

Got a suggestion to make Zingtree better? Give us a holler.

Zapier Decision Tree Integrations with Zingtree

zingtree zapier integration

Our Zapier app makes it easy to send data collected during each Zingtree session to more than 500+ applications supported by Zapier. In case you haven’t heard of it, Zapier is a tool that simplifies data exchange between various web applications. We’re big fans.

Here are some cool things you can do with Zingtree and Zapier:

  • Send data collected in a Zingtree session to Salesforce, Zoho, Highrise, or any other CRM.
  • Add an email address entered in a tree into Mailchimp.
  • Send  yourself an email or SMS message when a customer reaches a critical node in a tree.
  • Save new customer information in a Google Sheets row.
  • Create Trello cards from trees, and include customer notes and session data.
  • And tons more!

When using Zapier, you create “Zaps.” A Zap has a “trigger,” which is the source of the data, and an “action,” which is where the data gets sent. Most of our customers want to send data from Zingtree to another app, so we’ll demonstrate how this is done here.

Before starting, you may want to examine a demo tree from our Gallery that gathers data and sends it to Zapier, or copy it to your account.

How to Set up Zapier for Zingtree

The Zingtree Zapier app is currently invite-only. But if you’re reading this article, you’re invited!

  1. Create a free Zapier account at Zapier.com.
  2. Go here to accept an invitation to use the Zingtree app. The invitation appears:

    Accept the invite.
  3. You’ll be prompted to make a new Zap:
    Click Make a new Zap.
  4. You’ll be asked to choose a Trigger App, which is the source of the data exchange.
    Search for Zingtree, and select Zingtree (Beta).
  5. You’ll be asked to choose a single trigger.
    Click Save + Continue.
  6. Next, you’ll need to connect your Zingtree account, and a tree to Zapier.
    Click Connect a New Account. 
  7. You’ll be asked for your Zingtree API Key, which you can find here at the bottom of this page. Also enter the Tree ID that will be sending data to Zapier.
    Click Continue when finished.
  8. Change the name of the account, then click Test.

    You should see “success.” Click Save + Continue.
  9. Next, Zapier will attempt to retrieve any variables or sample data from your tree. If this is a new tree, you may want to run through it once and gather some data.
    Click Fetch & Continue.
  10. You’ll see some of the stock data that Zingtree always provides, as well as any custom data for your tree. Again, if you don’t see all the data you expect, do a test run through your tree, and enter some data at least once. This will make the rest of the process easier.
    Click Continue.

Set up the Action App – Email Example

So now you’re done with the Zingtree part. Congratulations! Next, you need to set up an Action App, which will receive data from Zingtree. Let’s set up email delivery as an action, as follows:

  1. Search for email, and choose Email by Zapier as an action app.
    Select Email by Zapier.
  2. This app has just one action.
    Click Save + Continue.
  3. Fill in details for the outbound email. You can insert fields from Zingtree in the body of the email as well.Click Continue when the email is set up correctly.
  4. You’ll see  a preview of what to expect.
    Click Create & Continue to save the action and send a test email.
  5. You should see another “success” screen.
    Click Finish when the email appears as you like.
  6. Name your Zap Zingtree to Email, and turn it on!

Your Zapier Zap is all set.

Making Zingtree Send Data

The final step is to tell Zingtree when to send all the data collected in a session to Zapier. This can be triggered from one or more nodes, when they are seen by the end-user of your tree.

  1. From Overview, Edit Node, edit the node that you want to trigger sending data to Zapier.
  2. Go to Send Message to, and pick Zapier: Zingtree to Email. This is the new Zap you created.
  3. Click Save.
  4. Now try a test from Zingtree. Using Preview or the Publish tool, navigate your tree, and when you reach the node that triggers the send, you should see something in your inbox. IMPORTANT: Make sure to use https in your published Zingtree URL when using Zapier.

Once you get your first Zap done, it becomes easy and addictive to hook Zingtree to the other applications that your business depends upon. So keep going!

Have any questions? Contact us anytime!

New Auto-Arrange Tool: Creating Nice Visual Layouts for Decision Trees

autoarrange-blog

When using the Zingtree Wizard, or the Excel or Google Sheets Import tools, one of the drawbacks is that when you view those trees in Designer, there is no initial data for the visual representation of your tree. We’ve been working on making sure the Traffic Map report and Designer views look good when you first open a tree not created with Designer, and now we finally have a solution: the Auto-Arrange Tool.

Auto-Arrange uses a combination of Artificial Intelligence and the laws of physics to come up with an optimal layout for your tree. It turns out that this is a difficult problem to solve, and while we feel it can be improved, this solution will save you a lot of time from manually rearranging the layout of your trees – especially really big ones.

One of the fun things about Auto-Arrange is that you can watch it working as it rearranges and repositions nodes in real-time.

auto-arrange-1

When you first open the Traffic Map report or Designer tool, you’ll be offered a chance to use Auto-Arrange. Next, Auto-Arrange will attempt to organize your decision tree in a tree-like fashion. If that doesn’t work, it will switch to a “network” view, which is less hierarchical. You can also switch views manually, and play with some of the parameters used to render the tree layout.

Here’s how our Pet Rock demo appears in Tree view (scaled down):

Here’s how the same tree looks in a Network display:

Once you are done playing with Auto-Arrange, you can proceed to Designer and your new layout will automatically become a part of the design.

Want to try it out? You can access Auto-Arrange from within Designer.

Is this new tool helpful? Fun? Let us know!

Update: Import from Excel, Google Sheets

NL-header-updates3

In spite of the fact that Zingtree has some really great ways to build interactive decision trees, we still get a lot of requests for making the process of creating trees even easier.  Many people are particularly comfortable working inside their favorite spreadsheet program, so we’ve created an easy way to use Microsoft Excel or Google Sheets to create new decision trees.

Once imported, the Zingtree editing and management tools can be used to refine and enhance your trees.

Here’s how our tutorial example appears in Google Sheets:

Details on this new feature:

Note that the same process for importing from Excel or Sheets can be used to import any tab delimited CSV file from any other program.

Other Updates

  • Update: Added ##ALL DATA## as a template for showing a summary of all data entry fields collected (h/t Sebastian, Logan). Details here.
  • Update: Added custom date range shortcut option to All Agents report. (h/t Allen J.).
  • Fix: Changing organization in All Agents report works properly now.
  • Fix: Restart function in older Zendesk Agent Scripting app installations now works properly again (Jamel).
  • Fix: Editing nodes from subtrees while using Preview now works properly (Jamel).
  • Update: Preview no longer automatically scrolls to the top of content.
  • Fix: Scoring uses numeric value of variables, not string value (Matt B.).
  • Update: All Agent report link added to My Agents page(Allen J.).
  • Update: Agent report now has quick date links.

Can we make your tree creating experience even easier? Just let us know!

Create Decision Trees using Google Sheets

sheets-blog

Did you know that Google Sheets can be used as a decision tree building tool? Using a specific layout, you can easily import any Sheets document into Zingtree, and turn it into a fully functional interactive decision tree.

Once you’ve successfully imported your tree, you can enhance it using Zingtree’s editing tools, which offer a lot more decision tree related functionality than Google Sheets.

Here’s how our example tree used in the tutorials appears in Sheets:

You can get started now by copying this example and modifying it:

Get Example from Google Sheets

 

Overview

Zingtree can create decision trees from Google Sheets, or any similarly formatted tabular source. Your spreadsheets just need to be set up in a specific way for this to work.

Here are the rules:

  1. The first row is for column headings. This is important, as it tells Zingtree what type of data is in each column. Make sure to use the column headings as described below.
  2. Column A is for the node number. Usually this is sequential. It’s required. The heading must say “Node“.
  3. Column B is for the title of a node. Your trees will be easier to read if each node has a descriptive title. The heading must say “Title“.
  4. Column C is for any content that appears in the content area.  This is imported as plain text, but you can add formatting, images, and videos later using the Zingtree editing tools. The heading must read “Content“.
  5. Column D is the question that is being asked. You can leave this blank if you want an answer node. The heading must be “Question“.
  6. If you want to include node tags in your tree, insert a column with a heading of “Tags“. This is optional.
  7. The last columns are for the button choices.  The heading over the first button column must be “Buttons“. You can have several columns of buttons.
  8. For the button columns, you can make them link to other nodes by adding the node number in square brackets.  In the above example, cell F2 has a button labelled “Yes” that links to node #2.  ( Yes[2]  )
  9. If you want to add a comment to any node, insert a cell on the right that starts with an exclamation point character (!).

Note: Columns can be in any order, but the column headings must contain the proper text like “Node”, “Question” etc.

You can also make Link Nodes and Tree Nodes with special text in the content column:

  • Example: To make a Link Node that goes to Google, the content area looks like this (see cell C8 in the example):
    LINK: http://google.com
  • Example: To make a Tree Node that opens tree ID #123456789, the content area will be (see cell C7 in the example):
    TREE: 123456789
  • Example: To make a Tree Node that opens tree ID #999999999 at node #3, the content area should be:
    TREE: 999999999,3

Once you’ve finished your tree, it needs to be exported as a TSV file. This is also known as tab-separated values, or tab delimited CSV.

You can also just copy and paste cells from Sheets into Zingtree. Sheets copies tab delimited data to the clipboard automatically.

Build Your Tree

To start, open this file in Sheets, and make a copy for your personal use. This is an enhanced demo from our “what to wear” example.

Now start modifying it.  Make sure to keep top row column headings in place. Keep questions in the question column, content in the content column, etc.

When you’re done, you can import your work into Zingteee via copy and paste, or by exporting to a tab delimited (TSV) file.

Import via Copy and Paste

This is the easiest way to import your decision tree into Zingtree:

  1. In Sheets, select the entire range of cells for your tree, and copy to the clipboard (Ctrl+C or Cmd+C).
  2. In Zingtree, go to the Import via Copy and Paste tool.  (You can also get there via My Trees, Create Tree, then select Import from Google Sheets.) A screen like this appears:

  3. Choose Google Sheets as the source.
  4. Enter a name for your tree
  5. Paste the data copied from step 1 into the data area. (Use Ctrl+V or Cmd+V).
  6. Click Import and Create Tree.

You’ll see your new tree in the Zingtree overview.

Import via a TSV file

For larger trees, you may find it better to upload a file instead of copying and pasting. Here’s how it’s done:

  1. In Sheets, go to File, Download As, and select Tab-separated values (.tsv, current sheet).

  2. In Zingtree, go to the Import File tool. (You can also get there from My Trees, Create Tree, and then choosing Import from Google Sheets.)

  3. If you want to overwrite an existing tree, select it via Replace Tree. Otherwise a new tree will be created.
  4. Click Import File, and locate the file you created in step 1.
  5. The new tree will appear in Zingtree.

Notes:

  • You can use this process to import files from any tab delimited CSV format.

Any questions? Reach out to us anytime. 

Create Decision Trees using Microsoft Excel

excel-blog

If you’re comfortable using Microsoft Excel, you can build the first draft of your Zingtree decision trees using a spreadsheet and then easily import them into Zingtree.

Once you’ve successfully imported your tree, you can modify it and enhance it using Zingtree’s editing tools, which offer a lot more decision tree related functionality than Excel.

Here’s how our example tree used in the tutorials appears in Excel:

Overview

Zingtree can create decision trees from Excel, or any similarly formatted tabular source. Your spreadsheets just need to be set up in a specific way for this to work.

Start now by downloading and modifying this example .XLS file:

Download Example for Excel

Here are the rules:

  1. The first row is for column headings. This is important, as it tells Zingtree what type of data is in each column. Make sure to use the column headings as described below.
  2. Column A is for the node number. Usually this is sequential. It’s required. The heading must say “Node“.
  3. Column B is for the title of a node. Your trees will be easier to read if each node has a descriptive title. The heading must say “Title“.
  4. Column C is the question that is being asked. You can leave this blank if you want an answer node. The heading must be “Question“.
  5. Column D is for any content that appears in the content area.  This is imported as plain text, but you can add formatting, images, and videos later using the Zingtree editing tools. The heading must read “Content“.
  6. If you want to include node tags in your tree, insert a column with a heading of “Tags“. This is optional.
  7. The last columns are for the button choices.  The heading over the first button column must be “Buttons“. You can have several columns of buttons.
  8. For the button columns, you can make them link to other nodes by adding the node number in square brackets.  In the above example, cell F2 has a button labelled “Yes” that links to node #2.  ( Yes[2]  )
  9. If you want to add a comment to any node, insert a cell on the right that starts with an exclamation point character (!).

Note: Columns can be in any order, but the column headings must contain the proper text like “Node”, “Question” etc.

You can also make Link Nodes and Tree Nodes with special text in the content column:

  • Example: To make a Link Node that goes to Google, the content area looks like this (see cell D9 in the example):
    LINK: http://google.com
  • Example: To make Tree Node that opens tree ID #123456789, the content area is this (see cell D8 in the example):
    TREE: 123456789
  • Example: To make a Tree Node that opens tree ID #999999999 at node #3, the content area should be:
    TREE: 999999999,3

Once you’ve finished your tree, it needs to be exported as a TXT file. This is also known as a tab delimited CSV.

You can also just copy and paste cells from your Excel document into Zingtree. Excel copies tab delimited CSV data to the clipboard automatically.

Build Your Tree

To start, download our “what to wear” example tree, as an Excel .XLS file.

Open this file in Excel, and start modifying it.  Make sure to keep top row column headings in place. Keep questions in the question column, content in the content column, etc.

When you’re done, you can import it into Zingteee via copy and paste, or by exporting to a TXT file.

Import via Copy and Paste

This is the easiest way to bring your decision tree into Zingtree:

  1. In Excel, select the entire range of cells for your tree, and copy to the clipboard (Ctrl+C or Cmd+C).
  2. In Zingtree, go to the Import via Copy and Paste tool.  (You can also get there via My Trees, Create Tree, then select Import from Microsoft Excel.) A screen like this appears:

  3. Choose Microsoft Excel as the source.
  4. Enter a name for your tree
  5. Paste the data copied from step 1 into the data area. (Use Ctrl+V or Cmd+V).
  6. Click Import and Create Tree.

You’ll see your new tree in the Zingtree overview.

Import via a TXT file

For larger trees, you may find it better to upload a file instead of copying and pasting. Here’s how it’s done:

  1. In Excel, go to File, Save As, and select Text (Tab Delimited) as the type.

  2. The file name will become the name of your tree. Click Save when finished.
  3. In Zingtree, go to the Import File tool. (You can also get there from My Trees, Create Tree, and then choosing Import from Excel.)

  4. If you want to overwrite an existing tree, select it via Replace Tree. Otherwise a new tree will be created.
  5. Click Import File, and locate the file you created in steps 1 and 2.
  6. The new tree will appear in Zingtree.

Notes:

  • You can use this process to import files from any tab delimited CSV format.

Any questions? Reach out to us anytime.