> For the complete documentation index, see [llms.txt](https://islamu.gitbook.io/islamu-event/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://islamu.gitbook.io/islamu-event/documentation/readme/integrations-and-ai.md).

# Integrations & AI

Webhooks, MCP, forms, moderation integrations, AI boundaries, and storage.

Every external integration maintains an explicit trust boundary, secret authority binding, replay/idempotency contract, readiness probe, and recovery runbook. Enabling a third-party provider never silently widens identity, payment, moderation, or multi-tenant boundaries.

***

## In this Section

* [**Webhooks**](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md) — Incoming payment/service callbacks and outgoing signed webhook delivery (Local HMAC vs. self-hosted Svix).
* [**Model Context Protocol (MCP)**](/islamu-event/documentation/readme/integrations-and-ai/mcp.md) — AI agent connectivity via Streamable HTTP, API key scoping, tenant gates, and human-in-the-loop proposal flows.
* [**Google & Microsoft Forms**](/islamu-event/documentation/readme/integrations-and-ai/google-and-microsoft-forms.md) — Ingest external questionnaires and surveys via Google Pub/Sub and Microsoft Power Automate.
* [**Coop & Osprey Moderation**](/islamu-event/documentation/readme/integrations-and-ai/coop-and-osprey.md) — Connect external community moderation queues and AI safety evaluation coordinators.
* [**Storage Providers**](/islamu-event/documentation/readme/integrations-and-ai/storage.md) — Local mounted filesystem vs. S3-compatible cloud object storage (MinIO, Cloudflare R2, AWS S3).

***

## Production Integration Invariant

Always test one valid operation and one rejected or replayed operation for every enabled external provider before opening public access.

***

## Related Guides & Next Steps

* [**Docker Compose Optional Profiles**](/islamu-event/documentation/readme/self-hosting/docker-compose.md#optional-service-profiles) — Enable `storage`, `authz`, `webhooks`, and `moderation` profiles.
* [**Environment Variables Reference**](/islamu-event/documentation/readme/configuration-and-operations/environment-variables.md#11-advanced-outgoing-webhooks-svix-infrastructure) — Environment dials for Svix, MinIO, Coop, and Osprey.
* [**Secrets Management**](/islamu-event/documentation/readme/configuration-and-operations/secrets.md) — Store webhook signing secrets and S3 access keys safely.
* [**Paid Events & Payouts**](/islamu-event/documentation/readme/events-and-ticketing/paid-events-and-payouts.md) — Stripe Connect webhook handling and payment finality.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://islamu.gitbook.io/islamu-event/documentation/readme/integrations-and-ai.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.