DEV Community: Truto

How to Choose a Unified API Provider

Truto — Sun, 19 Feb 2023 16:02:52 +0000

How to Choose a Unified API Provider

Choosing a unified API provider is easy. The parameters listed below will give you a good starting point for choosing a unified API provider.

Cost

You need to decide whether to buy or build. Addressing the buying vs. building question will take a whole post on its own. The jury is out though - buying is better in the long run if your core strength is not integrations.

That out of the way, the next thing you want to look at is the cost of the unified API solution now and as you scale in the future.

One of our mentors, Jayanth Mohana Krishna, said it just right:

"Most subscription-based SaaS tools tend to turn out expensive in the long run."

See if you can lock in a long-term deal with your unified API provider. This will make sure there are no surprises in the future and you are not suddenly forced to switch vendors on a fundamental part of your product offering.

Integrations/Connectors supported

It's always better to go with a unified provider that has a good roster of integrations/connectors. They should at least cover the top 5 solutions in each category because these are the integrations your customers are going to ask you for.

It'll also do good to get their thoughts on how frequently they add new integrations/connectors, how frequently they update their APIs to accommodate for changes in the underlying API, whether they support deprecated versions, and their integration roadmap (ideally they shouldn't have a roadmap). What's their assurance on turn around time for new integration/connector requests - 2 days, 7 days?

What's even better is the ability to add integrations on your own without having to depend on your unified API provider.

Documentation

It's important that your developers can find their way around easily instead of having to reach out to your unified API provider's support team or get on calls to figure things out (the irony).

Some unified API solutions like Truto are built to be intuitive from the ground up, so your dev team may not even have to refer to the docs. That said, it still helps to make sure the provider has robust documentation.

Operations supported

One of our customers saw a huge roster of integrations/connectors with one of our competitors, started a trial, and then things fell flat when they found out that all CRUD operations are not supported across most of their supported integrations/connectors. Most were read-only. Look for providers that support all CRUD operations across all endpoints that allow them.

Another extension of this is the number of endpoints supported - make sure that all the endpoints you need including those needed for edge cases are supported. What's sweeter is the ability for you to add endpoints on your own if needed.

Time to integrate the unified API solution

Imagine looking at using a unified API solution to fast-track integrations, and then staring at an integration timeline of 45 days to implement the unified API solution itself.

Look for implementation timelines—ahem, using timelines here doesn't feel apt. You should be able to hit the ground running in less than 30 minutes.

Longevity

You want to look for other customers that are using the product—how big are these customers, how long have they been using it, and what's their review of the platform.

You can also ask your unified API provider how long they have been in business and what their 1-, 2- and 3-year plans are.

Data storage

Get these questions addressed—Do they store the data on their servers? How frequently do their jobs run? Can you get data in real time if you want? How are the credentials stored?

Security

Your standard compliance checkpoints are here—SOC 2, ISO, GDPR, and CCPA. At least look for a letter of engagement for the frameworks under process.

Custom API integrations

Custom API integrations come in when one of your customers asks for integration with that obscure app nobody has heard of. It's important for you and your customer nonetheless. You still need to support it. Your sales team is probably behind you on it. It's for a big deal you don't want to lose.

Look for unified API providers that can build custom API integrations for you or give you the ability to do that. Otherwise, you'll end up spending time writing custom code for each of these integrations, with developer hours wasted on not just building the integrations but on maintaining them too.

Relevant:

Standards

Scalability

Some solutions from unified API providers work great while you're a small team with fewer customers. As soon as the number of jobs you run increases, you start to see cracks. This is going to affect your customers. Stale data, broken links, and broken workflows are problems you don't want as a growing company. Ensure that you ask questions about the unified API provider's tech stack and assess it for scalability.

Support

When shit hits the fan, you need to be able to get on the phone with someone. You need someone who's proactive. You need someone who's reachable by email. You need someone who's reachable by chat. You need someone who's there 24x7. Ensure that you have enough support behind you for that one day when things suddenly break. Ask for SLGs.

Here's a summary of the parameters:

Cost
Integrations/Connectors supported
Operations supported
Time to integrate the unified API solution
Longevity
Data storage
Security
Custom API integrations
Scalability
Support

Nice-to-haves in a unified API provider

Ability to add your own APIs

Cut to the chase when you want to add your own APIs instead of raising a request and waiting on your unified API provider to deliver on their roadmap.

Declarative

Simply tell the code what you want it to do without having to tell it how to do it. The power this will give your developers cannot be overstated.

Access to raw data

Your unified API provider does an amazing job abstracting data from various API sources. Makes it stupidly simple. That's great. No matter how well they do their job, you'll have to deal with edge cases from time to time. Make sure you are able to access the raw data when needed to deal with those.

Support for all CRUD operations

Most times, unified API providers get the read, and delete out of the way. They are the easiest to do. Make sure you also have support for create and update on all endpoints that allow them.

Sandbox accounts

Do they provide sandbox accounts for you to play around with to understand the product? Not just the sandbox account of their product but sandbox accounts for the integrations you are interested in.

Using your OAuth app instead of theirs

Imagine asking your users if "a third-party provider" wants access to their data vs. "your company name" wants access to their data.

Analytics

This will help you measure which clients are using the integrations effectively and which aren't. An important metric to track for your Customer Success team.

Here's a summary of the nice-to-haves:

Declarative
Access to raw data
Support for all CRUD operations
Sandbox accounts
Using your OAuth app instead of theirs
Analytics

Think we may have missed something here? We would love to hear from you and get your thoughts. Please write to us at marketing@truto.one

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started free

3 steps to integrate with Copper CRM using REST API

Truto — Thu, 16 Feb 2023 14:19:14 +0000

Truto's Integration GPS Series

Native integration with Copper CRM can be a huge time-saver to automate repetitive tasks. We have outlined the steps below to integrate with Copper CRM using their REST API below. Following these steps should save you immense time that would have otherwise been spent on unnecessary research and navigation.

Signup for Copper CRM

To start, sign up for Copper CRM by creating an account. Copper provides a free trial signup, so you can get started right away.

Get your API Key

Copper uses API key-based authentication, so you need to generate an API key to start making requests. To generate an API Key, go to the Settings tab on the sidebar and click Integrations, then API Keys. Click Generate API Key and Copper will provide you with a new API Key.

Generating a Copper CRM API Key

Make your First API Call

Before making your first API call, there are a few important things to keep in mind.

API URL

Copper's API can be found at https://api.copper.com/developer_api/

HTTPS

Copper uses HTTPS for their API. Make sure to use HTTPS for all requests.

Headers

Include the following headers in your requests:

X-PW-AccessToken: <Your API Key>
X-PW-Application: developer_api
X-PW-UserEmail: <Email address of the token owner>
Content-Type: application/json

Required headers for Copper CRM API

More info here.

Rate Limits

Copper limits API calls to 180 requests per minute. After reaching this limit, Copper returns a status code of 429.

Pagination

Copper uses page number-based pagination for their /search endpoints, which are mainly POST calls. You can sort results using sort_by and sort_direction. You need to provide the page_size and page_number in the request body.

More info here.

Code example

The following code example shows a typical request to the Copper API.

import requests

url = 'https://api.copper.com/developer_api/v1/search'
headers = {
    'X-PW-AccessToken': '<Your API Key>',
    'X-PW-Application': 'developer_api',
    'X-PW-UserEmail': '<Email address of the token owner>',
    'Content-Type': 'application/json'
}
payload = {
    "page_number": 1,
    "page_size": 50,
    "sort_by": "name",
    "sort_direction": "asc"
}

response = requests.post(url, headers=headers, json=payload)

Following these steps will you put on the right path to integrating Copper CRM.

Are you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Freshsales, and Microsoft Dynamics 365? Use Truto.one for free. It’s built for developers by developers to natively integrate all CRMs in one go.

If you have any questions or run into a roadblock, feel free to reach out to us at support@truto.one, we’ll be happy to help.

Integrating Salesforce Is Not As Hard As It Is Made Out To Be

Truto — Tue, 14 Feb 2023 06:14:29 +0000

We all know Salesforce to be a powerful CRM. While it is a powerful tool, it is often criticized for being clunky and difficult to integrate with other systems.

Traditionally, integrating Salesforce natively with other software could be a time-consuming and complex process. However, our integrations team has recently built an integration that was completed in less than four hours. More on that here. This is a testament to the recent improvements made by Salesforce, which have simplified the integration process.

The platform has undergone a significant overhaul in recent years, with a focus on making the interface more user-friendly and intuitive. This has not only made it easier for users to navigate and use the platform, but it has also made it easier to integrate with other systems.

The Salesforce API (Application Programming Interface) is well-documented and allows developers to integrate Salesforce with other systems easily. The API is available in both SOAP and REST formats, making it easy to integrate Salesforce with a wide range of systems, including custom-built applications.

This now begs the question, should you use a unified API provider to integrate Salesforce? You shouldn't if Salesforce is the only integration your teams/customers need. Go through the steps in this article and you should be up and running in less than an hour. We have distilled down the 4 hours of grunt work we did to just the steps you need to integrate Salesforce. (We integrated Salesforce using REST API)

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started free

Should I use a unified API provider?

Truto — Mon, 13 Feb 2023 05:57:01 +0000

Once you decide to use a unified format for your integrations, the next question that arises is whether you should use a unified API provider.

Using a unified API provider can come against the backdrop of what type of resources you have, how your company is set up and your upcoming strategies. Here are some considerations and how to make decisions based on them:

GTM

Are you looking at GTM sooner? In 2 weeks? or in 3 months? If your current resources are coming in the way of your GTM plans, you should use a unified API provider. Using a unified API provider can help you build an MVP that's built with what your customers need.

Resources

How big is your team currently? Is it just one co-founder who is writing all the code? Perhaps you made your first software engineer hire and they are building features? If this is how your team is set up you can use a unified API provider. Most times, the solution provided by the unified API provider will be able to match your demands as a growing company. If you feel that they may not be able to support you, you should consider moving things in-house or switching to another unified API provider.

No. of integrations

If you're looking at building just one or two integrations, then it's better you build them in-house. It might take a couple weeks but you don't have another tool to manage. And why pay for something when you cannot take full advantage of it?

If you're looking at integrating with a considerable number of applications, within a short time frame, then you should look at using a unified API provider. For example, Truto can help you go live with +200 apps in less than an hour.

Product roadmap

Is your product roadmap full of features to be built for customers and you are struggling to find spots to add the integrations your customers have requested? Then perhaps it's time to start using a unified API provider.

Maintenance

If integrations form a core part of your product, then you'll have to spend resources on maintaining them in the long run too. In 1 or 2 years, do you want to spend time and money on maintaining integrations from a strategic point of view? If the answer is no, you should look at using a unified API provider.

Effort vs ROI

If you need to build and maintain integration in-house, you'll need at least two full-time full-stack engineers working on them. The average salary for a full-stack engineer now is about $80k. That's $160k a year. You'll need to assess the prices quoted by your unified API provider and make a choice. Truto's cost for its unified API solution will make this choice a no-brainer.

Once you have decided to use a unified API provider based on these factors you will want to make sure you're choosing the best one. You should make sure that you are asking them these questions so you have a thorough understanding before choosing them.

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started free

10 Questions to ask your unified API provider

Truto — Tue, 07 Feb 2023 20:31:59 +0000

Integrations will form a core part of your product offering and its customer-facing. It's paramount that it just works 100% of the time. Use the questions below to make sure you don't end up firefighting one day.

Questions to ask your Unified API provider

What is your plan for the next 1,2 and 3 years?

Look for stability and clarity in thinking.

What is your product roadmap?

Look for features that will add value as time goes by. You don't want to use many SaaS products to get integrations done.

What's their plan for adding to their integrations catalogue?

Look for steady building activity on integrations. Make sure they will continue to support newer integrations. Better yet, ask them for custom integrations.

Who are your current customers?

Look for big well-known names here.

What is your tech stack?

Identify any gaps and make sure the tech stack is built for scale.

What happens if you choose to shut down the company?

Look for open-source solutions or solutions which have open-source elements in them. There are other solutions to alleviate this fear as well such as sharing the code base and self-hosted solutions.

Is a price increase on the horizon?

Since will be a fundamental part of your product offering, you want to make sure it doesn't become a burden later on. Make sure you have a long-term contract or a commitment to pricing caps.

Do you do multi-year contracts?

Any vendor will appreciate it when you ask them this question. The benefit you want to look for here for your team is a good price and/or services geared for you.

Will there be any issues when we scale?

This will bring out any gaps in the tech stack that may have been missed earlier.

How can we switch to another vendor?

If you are speaking with the right vendor, they will love this question and happily suggest how best to prepare for this event. Solutions you want to look for - help with migration, architecture design, and switching timelines.

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started free

What is API in simpler terms?

Truto — Thu, 02 Feb 2023 11:40:50 +0000

An API simply enables everyday apps you use to talk to each other. Google Analytics to talk to Slack. Salesforce to Gmail. PayPal to QuickBooks.

Before we dive deeper here's a response from chatGPT that'll set the context. We asked it to explain API to a 5-year-old:

Okay, let's imagine you have a toy chest with different toys in it. Each toy can do different things, like a toy car that can drive, a toy robot that can talk, and a toy boat that can float. But all these toys are closed boxes and you can't really play with them. But what if there was a magic key that can open the boxes? That magic key is called an API. When you use the key, it allows the toys to talk to each other and play together. It helps different toys to work together and makes playing with them more fun.

Let's see how this translates to your everyday work as a marketer, salesperson or HR executive -

Marketer

You are probably using an analytics tool such as Google Analytics. Now when there's a significant increase in traffic (>50%), you want to get an alert on your email. An API with an endpoint (fancy nomenclature for name) for traffic from Google Analytics will help make this happen. Your dev team will simply write a few lines of code that do the job of

monitoring the endpoint on Google Analytics for its value
set a threshold for the value (50%)
once the value crosses the threshold
send an alert to xyz@xyx.com

Salesperson

You are using a CRM such as Salesforce or HubSpot. When there's a new lead, you want to get an alert on Slack. The lead data is within Salesforce. Salesforce now needs to talk to Slack. Your dev team will simply write code that does the following:

monitoring the 'lead' endpoint on Salesforce every few hours
find when there's a new lead
if there's a new lead, send an alert to 'Slack user'

HR Executive

You are using an HRIS portal such as Workday or BambooHR and an ATS such as Lever or Greenhouse. When you mark a candidate as 'Hired' on Lever, you want that candidate to be created in BambooHR to being the onboarding process. Your dev team will set this up with a few lines of code:

monitor the 'candidate status' endpoint on Lever every few hours
when a candidate is marked as 'hired' >
fetch the following details - candidate name, candidate email, candidate phone, the candidate hired date
create a candidate on BambooHR with the fetched details

We hope this helped you understand what an API is in simple terms. To get the message across, we may have over-simplified how it works. It's important to note that the dev teams will spend quite some time trying to understand the API documentation of these apps and writing the code to make these integrations happen.

If you want to make it easier for your dev team, you can ask them to use tools like Truto.one, which will help them quickly set up these integrations for you.

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started free

The Dark Side of Directing Your Customers to Zapier for Integrations

Truto — Wed, 01 Feb 2023 17:56:37 +0000

When it comes to automating repetitive tasks, Zapier is a fantastic app that can be used for a variety of use cases. I'm a big fan too. It works well for internal teams that don't want to spend time building integrations for simple things like getting an update on Slack when a team member updates a cell in a Google Sheet.

When it comes to automating repetitive tasks, Zapier is a fantastic app that can be used for a variety of use cases. It works well for internal teams. I'm a big fan too.

As things are today, it may not be the best solution for your customers. There are solutions available that can help your team control all factors in an integration and ensure that your customers are 10x happier.

It's easy to claim your app integrates with 3000+ apps through Zapier. Have you ever wondered what happens on the other side? And what you can do to mitigate the issues faced by your customers?

Find out what happens on the other side and 8 reasons why you may not want to direct your customers to Zapier for integrations:

The User Experience

One of the most important factors to consider when it comes to integrations is the user experience. Your customers may not appreciate having to navigate to another app to complete an integration. This can lead to frustration and a negative experience with your product. By providing native integrations, you can keep your customers within your app and make the process seamless.

Zapier's Learning Curve

Zapier is a powerful tool, but it can be complex. This can lead to frustration and a negative experience with your product. You can make the process more user-friendly and remove the need to learn to use another app for your customers by writing just a few lines of code to offer the integrations within your app.

Is it just me or are some no-code solutions more confusing than just writing the code itself. 🤷‍♂️

— Founder Kyle (@kylekrzeski) January 17, 2023

Data Transfer Limits

Zapier has data transfer limits for each Zap, which can be a problem for serious apps that need to transfer large amounts of data. This can lead to delays and errors, which can negatively impact your customers. How would you feel if that happened during one of your demos to an important client? With native integrations, you can ensure that your customers can transfer data seamlessly without any limitations.

Troubleshooting

When things go wrong, it's important to have a reliable troubleshooting process in place. Your customers may not be happy if they miss important updates and tasks due to a Zap breaking, which can require time-consuming troubleshooting on their end. You eliminate the need for your customer to troubleshoot and make it easier for your customers to get things done by building native integrations for them.

Price

Zapier can be expensive, especially for small and medium-sized businesses. This can lead to financial constraints and a negative experience with your product.

Wow, Zapier pricing goes from $30/mo to $450 a month as soon as you want to “collaborate” (pool zaps across a team)? Fuck that pricing model. What are people using for alternatives?

— Andrew Kenney (@syrneus) April 26, 2022

Genuinely asking.

How do people afford Zapier? Am I misunderstanding how pricing works?

It seems ridiculously expensive. https://t.co/AGLw2MkrUJ

— Jack Polivka (@Jack_Polivka) January 24, 2023

Increased churn

Many B2B SaaS buyers move away from a product because it does not provide the necessary integrations or their experience while using the integration was broken. With broken Zapier integrations, your customers will move away by looking for alternatives and your competitors will have an edge. By providing native integrations, you can ensure that your customers have everything they need to be successful, which can reduce churn and increase customer satisfaction.

Customer effort vs your effort

"Keep it simple, stupid"

You don't want to make your customers go through hoops to get simple things done. By building native integrations for your customers you can ensure that your customers can get things done quickly and easily, without any effort on their part.

Limited Functionality

Zaps usually work in this format - 'If X happens on 1, do Y on 2'. And your customer is now creating a Zap between your app, 1, and another app, 2, say Google Sheets. While you may support all possibilities that your API allows, you customers are limited by the functionality that Zapier supports for Google Sheets. All your customers may not get what they want from this Zap, and you end up with unhappy customers who couldn't get simple things done. A native integration on the other hand, will allow your customers to do anything they want on Google Sheets with the data from your app.

Okay, what's the alternative?

We have said it enough - build native integrations. Turn the experience butter smooth. Get your customers to do all their tasks within your app. You get to fix any errors quickly without them even noticing. And the fastest way to build native integrations? Use Truto.one and build native integrations with 200+ SaaS applications for free. Reduce development time by 90% with Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting and 26 other categories.

Build +200 native integrations

Use Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started for free

Zapier: Read This if You Are Asking Your Customers to Integrate Using Zapier

Truto — Tue, 31 Jan 2023 06:53:13 +0000

When it comes to automating repetitive tasks, Zapier is a fantastic app that can be used for a variety of use cases. It works well for internal teams. I'm a big fan too.

It's easy to claim your app integrates with 3000+ apps through Zapier. Have you ever wondered what happens on the other side? And what you can do to mitigate the issues faced by your customers?

Find out what happens on the other side and 8 reasons why you may not want to direct your customers to Zapier for integrations:

The User Experience

Zapier's Learning Curve

Is it just me or are some no-code solutions more confusing than just writing the code itself. 🤷‍♂️

— Founder Kyle (@kylekrzeski) January 17, 2023

Data Transfer Limits

Zapier has data transfer limits for each Zap, which can be a problem for serious apps that need to transfer large amounts of data. This can lead to delays and errors, negatively impacting your customers. How would you feel if that happened during one of your demos to an important client? With native integrations, you can ensure that your customers can transfer data seamlessly without any limitations.

Troubleshooting

Price

Zapier can be expensive, especially for small and medium-sized businesses. This can lead to financial constraints and a negative experience with your product.

Wow, Zapier pricing goes from $30/mo to $450 a month as soon as you want to “collaborate” (pool zaps across a team)? Fuck that pricing model. What are people using for alternatives?

— Andrew Kenney (@syrneus) April 26, 2022

Genuinely asking.

How do people afford Zapier? Am I misunderstanding how pricing works?

It seems ridiculously expensive. https://t.co/AGLw2MkrUJ

— Jack Polivka (@Jack_Polivka) January 24, 2023

Increased churn

Customer effort vs your effort

"Keep it simple, stupid"

Limited Functionality

All your customers may not get what they want from this Zap, and you end up with unhappy customers who couldn't get simple things done. A native integration, on the other hand, will allow your customers to do anything they want on Google Sheets with the data from your app.

Okay, what can I use instead of Zapier?

And the fastest way to build native integrations? Use Truto.one and build native integrations with 200+ SaaS applications for free. Reduce development time by 90% with Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting and 26 other categories.

Build +200 native integrations

Use Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started for free

3 steps to integrate Microsoft Dynamics 365 Business Central

Truto — Sat, 28 Jan 2023 17:19:39 +0000

We have outlined the steps below to integrate with Microsoft Dynamics 365 Business Central below. Following these steps should save you immense time that would have otherwise been spent on unnecessary research and navigation.

If you are looking to natively integrate with all leading accounting applications such as QuickBooks Online, Wave, FreshBooks, Sage, and Xero? Use Truto.one’s Unified API for Accounting for free. It’s built for developers by developers to natively integrate all accounting applications in one go.

⚠️ This post is not an in-depth tutorial on how to build OAuth apps in general, some prior knowledge of how OAuth apps work is required.

Integrating with Microsoft Dynamics 365 Business Central REST API can be a great way to automate your business processes and improve your overall efficiency. In this blog post, we'll walk you through the steps to integrate with the Microsoft Dynamics 365 Business Central API by creating an Azure AD OAuth App and show you how it can benefit your business.

Sign up for a Microsoft Dynamics 365 Business Central account

Before you can start integrating with the Microsoft Dynamics 365 Business Central API, you'll need to sign up for a Microsoft Dynamics 365 Business Central account. You can sign up for a trial account or upgrade to a paid plan.

Create an application on Azure AD

Visit the App registration page on Azure AD
Click "New Registration"

Click New registration to start creating new OAuth app

Enter in the details of the app, with the redirect URI.
Select the account type based on whether you want to make this OAuth app available to others (Multitenant) or if you want to use it only in your organization (Single tenant).

Confirm the details before submitting

Submit the form by clicking "Register"
You can get your OAuth Client ID in the Overview tab, copy and store it somewhere.

OAuth Client ID is present in the Overview tab

On the app details page, click "Manifest" on the sidebar and change the value of allowPublicClient in the JSON editor to true

Update the manifest to allow public clients

Click "API permissions" and click "Add a permission"

Click Add a permission to add Dynamics CRM permission

Select "Dynamics 365 Business Central"

Select Dynamics 365 Business Central or search for it in the "APIs my organization uses" tab

Check "user_impersonation" permission and "Financials.ReadWrite.All" and click "Add permissions" at the bottom.

Select user_impersonation permission and Financials.ReadWrite.All, and save by clicking Add permissions

You can also grant admin consent for your organization by clicking, "Grant admin consent for ..."
Click "Certificates & secrets" and click "New client secret"

Create an OAuth Client Secret

Enter a friendly name for the secret and click "Add"

Enter a name and select the expiry duration

You will be shown the Client Secret for the OAuth app, copy it and store it somewhere safe.

Copy over the Client Secret

Post creating an OAuth application, you can either use Microsoft's Authentication libraries to add OAuth flow into your web application or any other OAuth client library, you can find the OAuth URLs and flows here.

IMPORTANT : When doing OAuth flow using a non-Microsoft library, add the Web API endpoint (which you'll find in the next section) as part of the scope. Add the following to the scope parameter -> https://api.businesscentral.dynamics.com/.default

Integrate with Microsoft Dynamics 365 Business Central API

Once you have your OAuth credentials and have granted the necessary permissions to your Azure AD OAuth App, you can start integrating with Microsoft Dynamics 365 Business Central API. The Microsoft Dynamics 365 Business Central API documentation provides detailed instructions on how to perform various actions, such as creating a customer, updating an invoice, and more. You can use any programming language that supports HTTP requests to communicate with the API.

Following these steps will you put on the right path to integrating Microsoft Dynamics 365 Business Central

If you have any questions or run into a roadblock, feel free to reach out to us at support@truto.one, we’ll be happy to help

Are you looking to natively integrate with all leading Accounting applications such as QuickBooks Online, Wave, FreshBooks, Sage, and Xero? Use Truto.one’s Unified API for Accounting for free. It’s built for developers by developers to natively integrate all accounting applications in one go.

Build +200 native integrations

Use Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started for free

3 steps to integrate with Zendesk Sell REST API using an OAuth App

Truto — Sat, 28 Jan 2023 17:14:50 +0000

Integrating with Zendesk Sell REST API can be a great way to automate your sales processes and improve your overall efficiency. In this blog post, we'll walk you through just the steps you need to integrate with Zendesk Sell API by creating an OAuth App.

If you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Freshsales, and Copper, use Truto.one for free. It’s built for developers by developers to natively integrate all CRMs in one go.

⚠️ This post is not an in-depth tutorial on how to build OAuth apps in general, some prior knowledge of how OAuth apps work is required.

Sign up for a Zendesk Sell account

Before you can start integrating with Zendesk Sell API, you'll need to sign up for a Zendesk Sell account. You can sign up for a free trial account.

Create an OAuth App

In order to authenticate and access the Zendesk Sell API, you need to create an OAuth App. To create an OAuth App,

Go to your Zendesk Sell account settings

Click Settings Icon

Type in oauth in the search bar and select OAuth

Type in OAuth into the sidebar search

Click on Developers App tab. Fill in the required details and click on Save.

Fill in the OAuth app details

Obtain your OAuth Credentials

Click Details to view the Client ID and Secret

After creating the OAuth App, you'll be provided with a client_id and a client_secret, along with the API Url. To view them, click the Details button in the OAuth app list. These credentials will be used to authenticate your requests when communicating with the Zendesk Sell API. Keep these credentials safe as they allow access to your Zendesk Sell account.

OAuth Endpoints

The OAuth URLs to initiate the OAuth flow are listed on Zendesk Sell's documentation which can be found here.

Scopes

The OAuth scopes used by Zendesk Sell's API can be found here.

Authorization format

Zendesk Sell API uses Bearer authorization, details can be found here.

Integrate with Zendesk Sell API

Once you have your OAuth credentials and have granted the necessary permissions to your OAuth App, you can start integrating with Zendesk Sell API. The Zendesk Sell API documentation provides detailed instructions on how to perform various actions, such as creating a lead, updating a contact, and more. You can use any programming language that supports HTTP requests to communicate with the API.

Test your integration

Before you go live with your integration, it's important to test it thoroughly. The Zendesk Sell API documentation provides examples of how to test different API calls, so you can make sure everything is working correctly. You can use tools like Postman to test your API calls.

Following these steps will you put on the right path to integrating Zendesk Sell.

If you have any questions or run into a roadblock, feel free to reach out to us at support@truto.one, we’ll be happy to help

Are you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Copper, and Microsoft Dynamics 365 Sales? Use Truto.one’s Unified API for CRM for free. It’s built for developers by developers to natively integrate all CRMs in one go.

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started for free

3 steps to integrate Salesforce using REST API

Truto — Sat, 28 Jan 2023 17:07:12 +0000

This blog will act as a reference for creating an OAuth web application for Salesforce to interact with the REST API. We have done the grunt work and have listed out just the resources you need to integrate.

If you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Freshsales, and Copper, use Truto.one for free. It’s built for developers by developers to natively integrate all CRMs in one go.

⚠️ This post is not an in-depth tutorial on how to build OAuth apps in general, some prior knowledge of how OAuth apps work is required.

Signup for a Salesforce Developer Account

Head on over to https://developer.salesforce.com/signup to sign up for a Salesforce Developer Edition account.

Salesforce Developer Edition Signup

Create a new Connected App

This is an OAuth app you will use to get the credentials for users and call the REST API endpoints

Search for "App Manager" in the search box on top of the screen.

Search for App Manager

Click "New Connected App" button on the top right corner of the screen

Create new Connected App

Punch in the basic information of the app

New Connected App Basic Information

In the API (Enable OAuth Settings) section, check Enable OAuth Settings. Fill in the callback URL, and make sure to select Manage user data via APIs (api) OAuth Scope along with other scopes required by your app. Check Enable Client Credentials Flow .

OAuth Settings for the Connected App

On the App's detail page, click Manage Consumer Details button, it will open a new tab and ask for an OTP sent to your email.

Button to view Client ID and Client Secret

After entering the OTP, you will see your Consumer Key (Client ID) and Consumer Secret (Client Secret) on the screen. Make a note of them.

Client ID and Secret

OAuth flow (Generating access tokens)

Once you have the Consumer Key and Consumer Secret, the OAuth flow Salesforce follows is pretty straightforward.

You can find all the OAuth Endpoints here. Use any OAuth client of your choice to initiate the OAuth flow.

Once you have the access_token, you can use Bearer authentication with the Salesforce REST API.

Following these steps will put you on the right path to integrating Salesforce CRM.

If you have any questions or run into a roadblock, feel free to reach out to us at support@truto.one, we’ll be happy to help

Are you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Copper, and Microsoft Dynamics Sales 365? Use Truto.one for free. It’s built for developers by developers to natively integrate all CRMs in one go.

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started for free

3 steps to integrate Microsoft Dynamics 365 Sales using Web API

Truto — Sat, 28 Jan 2023 17:01:09 +0000

This blog will act as a reference for creating an OAuth web application for Microsoft Dynamics 365 Sales to interact with the Web API. We have done the grunt work and have listed out just the resources you need to integrate.**

If you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Freshsales, and Copper, use Truto.one for free. It’s built for developers by developers to natively integrate all CRMs in one go.

⚠️ This post is not an in-depth tutorial on how to build OAuth apps in general, some prior knowledge of how OAuth apps work is required.

Prerequisites

You'd need a onmicrosoft.com account. If you don't have one, signup here.

Signup flow for Dynamics 365 Sales Premium Trial

At the end of the signup flow, you will end up at the Power Platform admin center. Just click "Cancel" when prompted to create an Environment.

Power Platform admin center

Sign up for Dynamics 365 Sales

Visit Dynamics 365 Sales Free Trial page and click on Try for free.
Enter your onmicrosoft.com email and click "Start your free trial".

Dynamics 365 Sales Free Trial Signup

Create an application on Azure AD

Visit the App registration page on Azure AD
Click "New Registration"

Click New registration to start creating new OAuth app

Enter in the details of the app, with the redirect URI.
Select the account type based on whether you want to make this OAuth app available to others (Multitenant) or if you want to use it only in your organization (Single tenant).

Confirm the details before submitting

Submit the form by clicking "Register"
You can get your OAuth Client ID in the Overview tab, copy and store it somewhere.

OAuth Client ID is present in the Overview tab

On the app details page, click "Manifest" on the sidebar and change the value of allowPublicClient in the JSON editor to true

Update the manifest to allow public clients

Click "API permissions" and click "Add a permission"

Click Add a permission to add Dynamics CRM permission

Select "Dynamics CRM"

Select Dynamics CRM or search for it in the "APIs my organization uses" tab

Check "user_impersonation" permission and click "Add permissions" at the bottom.

Select user_impersonation permission and save by clicking Add permissions

You can also grant admin consent for your organization by clicking, "Grant admin consent for ..."
Click "Certificates & secrets" and click "New client secret"

Create an OAuth Client Secret

Enter a friendly name for the secret and click "Add"

Enter a name and select the expiry duration

You will be shown the Client Secret for the OAuth app, copy it and store it somewhere safe.

Copy over the Client Secret

IMPORTANT : When doing OAuth flow using a non-Microsoft library, add the Web API endpoint (which you'll find in the next section) as part of the scope. For example, if your Web API endpoint is https://abcd.api.crm.dynamics.com/ , then add the following to the scope parameter -> https://abcd.api.crm.dynamics.com/.default

You can also test out the Dynamics 365 Sales API using Postman by following the instructions here.

Get your Web API Endpoint

Visit Power Apps dashboard.
Click the Environment selector on the top right and select the "Sales Trial" environment. This environment is created when you sign up for the trial of Dynamics 365 Sales on the first step.

Select the Sales Trial environment

Click the Cog icon beside the Environment selector and click "Developer resources"

Select Developer resources under the cog menu

The Web API endpoint will be listed.

Make a note of your Web API URL

For information on how to make requests, refer the guide by Microsoft here.

For information about the entities of Dynamics 365 Sales, refer the Web API reference.

Following these steps will you put on the right path to integrating Microsoft Dynamics 365 Sales CRM.

If you have any questions or run into a roadblock, feel free to reach out to us at support@truto.one, we’ll be happy to help.

Are you looking to natively integrate with all leading CRMs such as HubSpot, Close, Pipedrive, Freshsales, and Copper? Use Truto.one for free. It’s built for developers by developers to natively integrate all CRMs in one go.

Build +200 native integrations

Using Truto's Unified API for CRM, Unified API for ATS, Unified API for HRIS, Unified API for Accounting, and 26 other categories
Get started free