insites

Routing Insites interactions to the correct module sub-skill is automated by referencing a specific module like CRM, Pipelines, Data, Events, Globals, or CMS, which directs the request to the appropriate handler. If no specific module is mentioned, the entry point still routes based on context.

The best way to integrate with Insites modules across instances is using an entry-point router that applies secure API usage and environment variables. This ensures consistent, versioned access to CRM, Pipelines, Data, Events, Globals, and CMS sub-skills.

No, you do not need to specify a module to trigger Insites routing. The entry point automatically identifies which module sub-skill to engage for CRM, Pipelines, Data, Events, Globals, or CMS tasks based on the interaction context.

To set up secure API usage for Insites module integrations, define environment variables and follow the setup guidance provided by the routing skill. This ensures consistent and safe access across all module sub-skills within your Insites instance.

Yes, you can use Insites routing for both CRM and CMS tasks. The router handles module-level tasks across CRM, Pipelines, Data, Events, Globals, and CMS, directing each interaction to the correct sub-skill for processing.

Insites module interactions may not route correctly if the referenced module is not recognized or if environment variables are not properly defined. Ensure the module name matches CRM, Pipelines, Data, Events, Globals, or CMS, and verify secure API setup for consistent integration.