POWERFUL PLATFORM - VENDOR REGISTRATION SAMPLES v1
Published: 2026-10-16

These are sanitized learning copies of the supplied GET and POST Power Automate export packages. They are not a complete turnkey deployment, and import/run success has not been tested in a Microsoft tenant.

CONTENTS
GET: HTTP GET trigger, an HTML/JavaScript registration form, and an HTML response.
POST: HTTP POST multipart input, SharePoint item creation, one file-write branch, and a link back to the created item.

SANITIZATION
Removed the embedded signed POST endpoint, connection email, creator/tenant/migration metadata and source timestamps. Replaced SharePoint site/list/library/folder references, original flow/resource identifiers and connection identity. Replaced client-specific labels. Original files were not modified or published. Field labels such as Vendor Email, Contact Name, Phone and Address remain as empty input definitions; no real submitted values or attachments are included.

SETUP
1. Import into a development environment as NEW flows. The package suggests New rather than updating an existing flow.
2. For POST, select a new SharePoint connection and replace RECONNECT_SHAREPOINT through the import/designer configuration.
3. Replace all example.invalid URLs, zero-GUID list placeholders, document-library and folder placeholders in the POST flow.
4. Create your own list and map the fields. Existing item/field_N internal names are example source mappings, not a portable list schema.
5. Configure the imported POST trigger for your intended access model. Save it and use YOUR new POST endpoint in the GET flow's VarFlowUrlPostRequest variable. Never use an original client endpoint.
6. Review trigger authentication settings, endpoint protection and licensing before exposing the form. The source request-trigger authentication setting was preserved; this is not a recommendation to enable anonymous access without controls.
7. Test with synthetic values and non-sensitive dummy files. Confirm actual SharePoint persistence before displaying success to visitors.

KNOWN SAMPLE LIMITATIONS
- The original POST package writes only one file (multipart part 13). The GET form includes multiple upload inputs; the other attachment paths are not implemented in this supplied POST sample.
- The source file-write action uses the fixed filename test.csv. Replace it with an appropriate unique filename and handle file types before testing repeated submissions.
- Numeric triggerMultipartBody positions depend on the form field order. Optional unchecked radio groups can shift the payload; make choices explicit or redesign parsing by field name.
- Review the source base64ToBinary conversions for text fields and remap their output types to your destination schema.
- Some form inputs, including Message and additional attachment/date fields, are not mapped to POST actions.
- The POST sample has no explicit final HTTP Response action. An HTTP acceptance response is not proof that all downstream actions succeeded.
- Validate content, size, extension and upload permissions. Add duplicate handling, abuse protection, error handling and appropriate retention before production.
- A browser-delivered JavaScript endpoint is visible to visitors. Keep credentials and privileged endpoints out of public JavaScript; evaluate a controlled server-side gateway where appropriate.
- The form references public Bootstrap/jQuery/Popper assets. Review or self-host these dependencies for your deployment.
- No licenses were assigned to external registrants in the described project. These sample files do not remove Microsoft platform licensing requirements.

VALIDATION PERFORMED
All ZIP entries parsed as JSON; ZIP CRC checks passed. Package resource/asset/dependency mappings and action runAfter references were checked. No email addresses, original identity/resource GUIDs, original site/connection values or signed callback URL remained after sanitization. This is static validation, not a tenant import test or certification of production security.

Read the case study at https://www.powerfulplatform.net/case-study-anonymous-vendor-registration-into-sharepoint/
