Connecting your data to Wordnerds through input API
We'll run through the benefits and process for creating a live connection to your data (and saying goodbye to manual uploads👋).
There are two ways to get your data into the Wordnerds platform. We generally recommend everyone starts with a manual upload. For details on how to do that see our guide. For those who are ready for an automated data stream, you'll want to connect to our input API.
What is an API?
An API stands for Application Programming Interface. It’s essentially a bridge between two platforms that allows data to be passed from one to the other.
What is it good for?
- Giving you real time insights from live data.
- For high volume, regular data flows such as contacts through your CRM.
- Reduces time spent on manually uploading.
- Secure way to send Wordnerds data if there are DPIA issues over email/shared files.
How do I get started?
1. First step is to understand how you want your data to look in the platform. If you already manually upload your data you'll likely have a template you can use to get started. If not, your CSM will support you to map out the fields you need.
2. Reach out to your IT/engineering team to book in time for them to complete the build. Introduce them to your CSM who can share all the information they'll need including credentials for a sandbox testing area, the data mapping document and the Wordnerds API documentation.
3. Your CSM will set up a call between the engineering teams from both parties and the platform user to review the results in the testing area. This is a chance to ask questions, address any queries and make sure the data is coming in the way we'd expect. Following that, your team should be able to connect to the main project and let the data start flowing in!
Clean it up 🧼 🫧 🧽
To get the most value out of the data you send to the Wordnerds Platform, it is best to clean it up before sending it. When you ask your technical team to integrate different data sources, you should work with them to ensure only the data you want to analyse is passed across.
Email data:
- Make sure you filter the raw email content for the useful part, you want the plain text version of the email (not HTML and not a raw email meant for your email client)
- You normally won’t want a full email thread every time. Ask your team to filter for just the most recent message in the thread. Libraries like this can be helpful.
Call transcripts:
- Are you interested in both sides of the conversation? Normally the useful part is what your customer is saying.
- Are you interested in the full call transcript? The useful information is normally at the start, this can clear up noise in your data and reduce your costs.
CRM/Other integrations:
- Often, structured data (standard questions, account numbers, names) are brought across as text content, this will give worse results. This kind of data can be brought in as metadata or themes. Text content should normally be words directly from your customer.
FAQs
Can I delete data that’s come through via API?
Yes, just send a request to the CSM with the project that you’d like the data to be deleted from as well as the segment of data you want deleted. We might need information like a reference ID or a date range.
Are there any limits on the length of brand/theme/header names?Yes, they cannot be longer than 191 characters.
Can I get historic data in via API too?Yes, ultimately you're in control of the data being sent. You may want to send data as soon as it becomes available or in batches at longer intervals. Speak with your Wordnerds CSM to discuss what will work best for you.
Our supplier wants Wordnerds to pull data from their software instead. Is this doable?Unfortunately not. Our Input API documentation is written so data providers/agencies push the data to us, rather than us writing bespoke code for each customer to pull data into the platform.
What happens if question wording and fields change?Data will stop coming into the platform until the question wording is changed within the API code.
How long will this take to be fully automated?Because all datasets are so different, dev team workloads vary and customer needs are sometimes very bespoke, it can be difficult to estimate exactly how long it will take for data to be flowing in without a hitch. However, in our experience, as long as the respective dev teams meet ASAP and required fields are confirmed, this whole process should take approximately 3 weeks.
More questions?
We’re always happy to chat. Reach out using the help bubble at the bottom of your screen or contact your Customer Success Manager.
✍️ Article written by: Lyndsay, Senior Customer Success Manager