Concepts

This picture illustrates the concept of an Integration App that has Actions, that are used in Steps in an Integration. All data that is queried and attached is available as StepData during the entire execution of the integration.

When should we use Copyl Integration Platform, and when not?

Evaluating When to Use the Integration Platform

Getting Started

Setup Copyl Integration Platform in your API (.Net)

Two ways – pre-defined Triggers or ad-hoc Triggers

Pre-defined Triggers

These triggers must be defined in Copyl before you send events to them. This method is best for organizations that plans the integrations before implementing them.

Pros:

• Well-structured integration plans.
• Can set up integrations before the Trigger is generating events.
• You don’t have to be a developer to design the Trigger.
• Code generator has defined fields that the developer fills with data.

Cons:

• Must define the Trigger in Copyl and before you can implement it in the code.

Automatically defined Triggers

This is the recommended way to define Triggers. Just add a line to your Create, Update and Delete operations in your API, and the Trigger will be created upon first call.

await CopylIntegrationPlatformHelper.SendEventToCIPAsync(_configuration, ***YOUR_OBJECT***, MethodBase.GetCurrentMethod().Name);

See Getting Started.

Integrating Triggers in your source code

https://www.loom.com/share/346ace17a84247fca6a2fc6b454f4cc2?sid=02e98441-a34d-4861-b5a9-2d9993e446c3

Features

How to set up a Datawatcher for effective data monitoring

Integration Connectors

Scripting Support in Integrations

Glossary

How to avoid Vendor Lock-In for your integration solution