Modern embedded integration platforms make it simple to export your workflows from your development environment in formats such as JSON documents and import them into your production environment, either manually or by using GraphQL APIs to automate the process. Check for complete log management and diagnostics Robust logging and clear error codes and diagnostics are crucial for quickly resolving customer and integration issues. When debugging more-complex workflows, logging and error codes are also vital so developers can see what each workflow step receives (such as the input) and compare it to what they expect to happen. Look for embedded integration platforms that: - Indicate which runs are successful, processing, failed, or stopped - Provide an easy way to drill down into any workflow to view how many steps your workflow has completed and their status - Has robust search built-in, with the ability to filter for factors such as all executions before or after a specific date, or based on successful, failed, running, or specific workflow steps. - Ensure transparency into data and execution behind each step in a workflow, showing inputs, outputs, and data, ideally in standard formats such as JSON. 8. Ensure options for both productized and services-led integrations Take a close look at your company’s current integration trajectory, and you’ll see two distinctly different delivery models. You may not even need both now, but you may end up growing from one into the other in the future. Productized integrations One delivery model is productized integrations. We’re talking about relatively cookie- cutter integrations that you can provide in-product or via an integration marketplace. Such integrations will vary little from customer to customer. You can handle any differences across customers by parameters that customers can fill out when they self-activate the integration within your product. Typically, your development team will build and maintain productized integrations (such as syncing customer data between a particular cloud app and your product), since such integrations are generally for self-activation at scale across your customer base. 19