Connectors & integrations

Teams Approvals & Power Automate

Microsoft Teams Approvals and Power Automate stay fully supported for direct webhooks. SharePoint folder bindings handle everyday contract intake, and these endpoints remain available whenever you want them.

How intake works today

SharePoint folder bindings are the primary intake path: bind a folder and a scheduled background job ingests new files automatically, with fewer moving parts to maintain. Power Automate flows that push SharePoint events to /api/intake keep working alongside it. See Ingestion.

What remains

POST /api/intake: direct webhook intake for systems that already push PDFs.
POST /api/workflows/renewal-decision
POST /api/workflows/amendment-approval
POST /api/workflows/deviation-approval
POST /api/notify/teams: emit an Adaptive Card to a Teams channel.

These endpoints accept Adaptive Card payloads from Teams Approvals / Power Automate flows. Tenants that have invested in those flows keep them, and they sit comfortably alongside folder bindings.

Bring your own flows

You build Power Automate flows against these endpoints and version them in your own environment, giving you full control over the flow logic.

Procurement

Branding