Introduction to Embedded iPaaS

This portion of the documentation is intended for software developers looking to add integration capabilities to their own applications. With Monkedo’s embedded iPaaS (Integration Platform as a Service), developers can build internal workflows and offer seamless, customer-facing integrations so end-users can connect their third-party apps directly within your software. If you aren’t developing your own software or don't need to add integrations, you will not need these features.

Embedded iPaaS is a cloud-based platform that enables seamless connectivity, data integration, and automation between diverse applications. It allows organizations to streamline workflows and data sharing without extensive custom development.

Monkedo serves as both a no-code automation platform and an embedded iPaaS. It acts as a central integration hub in the cloud, providing:

• Centralized Integration Platform: Unify data across various tools and automate workflows with minimal effort.

• No-Code Environment: Use our intuitive automation editor to set up integrations easily, allowing even non-developers to build them.

• Scalable Cloud Infrastructure: Reliably handle large volumes of data as your integration needs grow.

• Secure Data Handling: Ensure data privacy with built-in encryption and secure token storage.

• Authentication Management: Automatically handle OAuth, API keys, and other authorization flows across integrated systems.

Monkedo’s embedded iPaaS allows you to build two key types of integrations for your application:

1. Internal Integrations: Connect your company’s own third-party accounts to enhance your app’s internal functionality.

2. Customer-Facing Integrations: Allow your users to connect their own third-party accounts, enabling seamless data syncs between your app and the software they already use.

Since Monkedo already offers robust automation features, no additional setup is needed for internal use cases. You can easily set up bidirectional workflows:

• From Your App to Other Apps: Send an HTTP request from your app to a Monkedo Webhook Trigger to initiate an action in a third-party app.

• From Other Apps to Your App: Use triggers in Monkedo to send data back to your software via HTTP requests.

The remainder of this documentation will focus specifically on customer-facing integrations.

Customer-facing integrations let your users link their own third-party accounts to your app. With Monkedo’s embedded iPaaS, this entire process is handled in the background. Your users never see Monkedo or leave your application.

For example, if you are building an event management tool, your customers might want to sync their events with Google Calendar or receive Slack notifications. Building this from scratch means managing OAuth, storing access tokens, and studying external API documentation, a complex and time-consuming process.

Monkedo manages these complexities for you so you can focus on your core product:

• Authorization Handling: Monkedo’s Frontend SDK manages all authorization flows (from API keys to OAuth 2.0). It handles the required dialogs and redirects to the third-party app’s authorization page without you having to write the code.

• Secure Token Storage: Monkedo securely requests and stores access tokens and API keys, sparing you the burden of credential management.

• Calling The API: Use Monkedo’s pre-built app components to interact with third-party APIs effortlessly.

• Workflow Automation: Use the no-code editor to design workflows (like creating a calendar event or sending a Slack message) and trigger them via the Monkedo API.

• Automatic Token Refreshing: Monkedo automatically refreshes expired tokens, eliminating the need for you to manage token lifecycles.

Getting Started with Customer-Facing Integrations

Implementing Monkedo’s embedded iPaaS is straightforward:

1. Setup Project: Enable Developer Mode in your Monkedo Profile, create a project for your app, and select the third-party apps you want to offer to your users.

2. Create Automations: Use the no-code editor to build the specific actions you want to perform on the integrated apps.

3. Start Authorization: Add the Monkedo Frontend SDK to your app. Call the authorization function to let Monkedo handle the necessary user logins and modal pop-ups.

4. Run Automations: Call Monkedo’s API to trigger your automations. By passing a specific user's ID in the API call, the automation will securely use that user's connected credentials to perform personalized actions on their behalf.

The best part is that this all happens seamlessly for the user. While Monkedo works in the background to manage the integration, users only interact with your application.