> 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/google-and-microsoft-forms.md).

# Google & Microsoft Forms

Integrate Google Workspace and Microsoft 365 Forms through their bounded supported contracts.

Organizers can map external survey tools (Google Forms and Microsoft Forms) directly into event attendee records. The platform ingests external form responses and projects them into native [Custom Properties](/islamu-event/documentation/readme/events-and-ticketing/custom-properties.md) without compromising attendee identity truth.

***

## 1. Google Forms (Google Workspace)

The Google Forms integration is designed for Google Workspace organizations:

* **Authentication**: Uses tenant-owned Google OAuth 2.0 and Google Forms REST API.
* **Notification Flow**: Employs OIDC-authenticated Google Cloud Pub/Sub topics. Pub/Sub messages act as notify-only triggers: the platform queues an authenticated fetch back to the Google Forms API to read the authoritative responses.
* **Limitations**: File-upload questions and live submission writebacks are not supported.

***

## 2. Microsoft Forms (Microsoft 365)

Microsoft Forms integration targets Microsoft 365 organizational tenants using an organizer-owned Power Automate connector flow (`POWER_AUTOMATE_V1`):

* **Activation**: Requires a dedicated binding callback key and field mapping configuration.
* **Delivery**: Power Automate pushes response envelopes to the platform's incoming callback route.
* **Payload Verification**: Payloads are idempotently ingested and matched against registered attendee tickets (see [Ticketing & Check-In](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md)).

***

## 3. Data Reconciliation & Privacy Boundaries

External form correlation connects questionnaire answers to existing event registrations:

* It never manufactures new user accounts or bypasses [Keycloak Authentication](/islamu-event/documentation/readme/security-and-identity/authentication.md).
* Answers are subject to the same privacy ceilings and GDPR purge rules as native questions (see [Privacy Erasure & GDPR Compliance](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md)).

***

## Related Guides & Next Steps

* [**Custom Properties Governance**](/islamu-event/documentation/readme/events-and-ticketing/custom-properties.md) — Learn how long-tail attendee data is governed and purged.
* [**Ticketing & Check-In**](/islamu-event/documentation/readme/events-and-ticketing/ticketing-and-check-in.md) — Map questionnaire responses to admission tickets.
* [**Webhooks & Callbacks**](/islamu-event/documentation/readme/integrations-and-ai/webhooks.md) — Understand incoming webhook signatures and idempotency.
* [**Privacy Erasure & GDPR**](/islamu-event/documentation/readme/security-and-identity/privacy-erasure.md) — Scrubbing attendee responses upon account deletion.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.