Skip to main content

​
Integrations power agent templates

Decisional integrations are not just app connections. They are the read tools, write tools, triggers, files, and approval surfaces that let an agent complete a workflow end to end. The public template library shows the pattern clearly: each template combines a trigger, one or more connected systems, AI or data-processing steps, and a final output that is ready for review or downstream use. At the platform level, each integration exposes tools, and each tool can use one or more credentials. Access-control policy decides which tools and credentials an agent can use and whether a tool call needs approval.

Browse Agent Templates

See the live template library on decisional.com.

​
What agents connect

Triggers

Start agents from schedules, integration events, webhooks, form submissions, chat requests, or manual runs.

Source systems

Pull context from inboxes, CRMs, spreadsheets, files, meeting notes, payment systems, issue trackers, and web sources.

Actions

Send messages, update records, create documents, write spreadsheets, archive files, comment on PRs, or notify reviewers.

Outputs

Produce review packages, spreadsheets, documents, approval requests, summaries, exception notes, and audit-ready archives.

​
Template-backed integration patterns

Use these public templates as examples of how integrations work together in real workflows.

​
Common integration bundles

Templates usually combine several integration types rather than relying on one tool alone.
Finance templates often combine payment or invoice systems with spreadsheets, file storage, email, and approval messaging. This pattern is useful for invoice archiving, close support, procurement review, and exception handling.
GTM templates combine CRM records, inbox context, enrichment tools, spreadsheets, documents, and chat notifications. This pattern is useful for lead scoring, follow-up drafting, account research, and CRM hygiene.
Product and engineering templates connect repositories, issue trackers, call transcripts, chat, docs, and spreadsheets. This pattern is useful for PR review, shipping reports, call issue detection, onboarding, and webhook-driven notifications.
Operations templates combine email or forms with spreadsheets, file storage, and generated outputs. This pattern is useful for quotes, drawings, inbox routing, and lightweight back-office workflows.

​
Trigger types

Templates use a small set of repeatable trigger patterns.

​
How to choose integrations

1

Start with the output

Decide what the agent should produce: a spreadsheet, document, email, CRM update, approval request, archive, or notification.
2

Pick the trigger

Choose whether the work should start on a schedule, from an app event, from a webhook, from chat, from email, or manually.
3

Add the source systems

Connect the systems the agent needs to read from, such as inboxes, CRMs, spreadsheets, issue trackers, meeting tools, payment systems, or files.
4

Add the action systems

Connect the systems the agent needs to write to, such as chat, email, spreadsheets, documents, file storage, CRMs, or code review tools.
5

Set approvals

Use approval policy for write actions, customer-facing outputs, financial operations, and any step where a human should review before the agent proceeds.

Approvals and Policy

Learn how tool policies, approval modes, and bypass approvals apply to integration actions.

Credentials

Learn how integrations, tools, credentials, and access-control policy fit together.

​
Connect integrations

You can connect tools ahead of time from the Integrations page in the app, or connect them during agent setup and agent runs when Decisional asks for access.

Build from a template

Start from a public template and connect the required systems during setup.

Create your own agent

Describe the workflow in the Decisional web app, then connect the apps it asks for.