Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Microsoft 365 People

Manage contacts in Microsoft 365 People

CategoryOther
Authenticationcustom
Version0.3.0
Published scopes0 published scopes
Last updatedSeptember 21, 2026

Overview

Connect Microsoft 365 People with Flows360

Manage contacts in Microsoft 365 People

Use the Microsoft 365 People connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 7 actions and 1 trigger.

Available actions

  • Create a Contact
  • Delete a Contact
  • Update a Contact
  • Create a Contact Folder
  • Get a Contact Folder
  • Search Contacts
  • Custom API Call

Available triggers

  • New or Updated Contact

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Microsoft 365 People
  • Package: @activepieces/piece-microsoft-365-people@0.3.0
  • Exact artifact digest: sha256:b8e544df2d3b271e64cc97b0d26ad5676d9ab062aa73f4b82e7a9deffb426e6d
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Create a Contact (createContact), Create a new contact in People with detailed attributes (email, phone, address, etc.). Classification: read.
  • Delete a Contact (deleteContact), Permanently remove a contact. Classification: read.
  • Update a Contact (updateContact), Modify fields of an existing contact. Classification: read.
  • Create a Contact Folder (createContactFolder), Organize contacts by adding a new contact folder. Classification: read.
  • Get a Contact Folder (getContactFolder), Retrieve metadata (name, ID) of a specified contact folder. Classification: read.
  • Search Contacts (searchContacts), Find contacts by name, email, or other properties. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New or Updated Contact, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects8
Supported actions7
Triggers1

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access token Required · protected credential
  • Cloud Environment Required

Supported objects

ObjectReadWriteNotes
Create a Contact Yes No Create a new contact in People with detailed attributes (email, phone, address, etc.).
Delete a Contact Yes No Permanently remove a contact.
Update a Contact Yes No Modify fields of an existing contact.
Create a Contact Folder Yes No Organize contacts by adding a new contact folder.
Get a Contact Folder Yes No Retrieve metadata (name, ID) of a specified contact folder.
Search Contacts Yes No Find contacts by name, email, or other properties.
Custom API Call Yes No Make a custom API call to a specific endpoint
New or Updated Contact Yes No polling trigger declared by the pinned package.

Supported actions

Create a Contact · Read

Create a new contact in People with detailed attributes (email, phone, address, etc.).

create_contact · Risk: low · Retry: safe

Inputs

  • displayName · string · Optional
  • givenName · string · Optional
  • middleName · string · Optional
  • surname · string · Optional
  • emailAddresses · array · Optional
  • mobilePhone · string · Optional
  • assistantName · string · Optional
  • birthday · string · Optional
  • businessStreet · string · Optional
  • businessCity · string · Optional
  • businessState · string · Optional
  • businessPostalCode · string · Optional
  • businessCountryOrRegion · string · Optional
  • children · array · Optional
  • companyName · string · Optional
  • department · string · Optional
  • homeStreet · string · Optional
  • homeCity · string · Optional
  • homeState · string · Optional
  • homePostalCode · string · Optional
  • homeCountryOrRegion · string · Optional
  • imAddresses · array · Optional
  • initials · string · Optional
  • jobTitle · string · Optional
  • manager · string · Optional
  • nickName · string · Optional
  • officeLocation · string · Optional
  • otherStreet · string · Optional
  • otherCity · string · Optional
  • otherState · string · Optional
  • otherPostalCode · string · Optional
  • otherCountryOrRegion · string · Optional
  • parentFolder · string · Optional, Select a parent folder
  • personalNotes · string · Optional
  • profession · string · Optional
  • spouseName · string · Optional
  • title · string · Optional
Delete a Contact · Read

Permanently remove a contact.

delete_contact · Risk: low · Retry: safe

Inputs

  • contactId · string · Required, Select a Contact
Update a Contact · Read

Modify fields of an existing contact.

update_contact · Risk: low · Retry: safe

Inputs

  • contactId · string · Required, Select a Contact
  • displayName · string · Optional
  • givenName · string · Optional
  • middleName · string · Optional
  • surname · string · Optional
  • emailAddresses · array · Optional
  • mobilePhone · string · Optional
  • assistantName · string · Optional
  • birthday · string · Optional
  • businessStreet · string · Optional
  • businessCity · string · Optional
  • businessState · string · Optional
  • businessPostalCode · string · Optional
  • businessCountryOrRegion · string · Optional
  • children · array · Optional
  • companyName · string · Optional
  • department · string · Optional
  • homeStreet · string · Optional
  • homeCity · string · Optional
  • homeState · string · Optional
  • homePostalCode · string · Optional
  • homeCountryOrRegion · string · Optional
  • imAddresses · array · Optional
  • initials · string · Optional
  • jobTitle · string · Optional
  • manager · string · Optional
  • nickName · string · Optional
  • officeLocation · string · Optional
  • otherStreet · string · Optional
  • otherCity · string · Optional
  • otherState · string · Optional
  • otherPostalCode · string · Optional
  • otherCountryOrRegion · string · Optional
  • parentFolder · string · Optional, Select a parent folder
  • personalNotes · string · Optional
  • profession · string · Optional
  • spouseName · string · Optional
  • title · string · Optional
Create a Contact Folder · Read

Organize contacts by adding a new contact folder.

create_contact_folder · Risk: low · Retry: safe

Inputs

  • displayName · string · Required
  • parentFolder · string · Optional, Select a parent folder
Get a Contact Folder · Read

Retrieve metadata (name, ID) of a specified contact folder.

get_contact_folder · Risk: low · Retry: safe

Inputs

  • contactFolder · string · Required, Select a contact folder
Search Contacts · Read

Find contacts by name, email, or other properties.

search_contacts · Risk: low · Retry: safe

Inputs

  • searchValue · string · Required, Find contacts by name, email, or other properties.
Custom API Call · Read

Make a custom API call to a specific endpoint

custom_api_call · Risk: low · Retry: safe

Inputs

  • url · object · Required
  • method · string · Required
  • headers · object · Optional, Authorization headers are injected automatically from your connection.
  • queryParams · object · Optional, Appended to the URL as ?key=value.
  • body_type · string · Optional
  • body · object · Optional
  • response_is_binary · boolean · Optional, Enable for files like PDFs, images, etc.
  • failsafe · boolean · Optional, On a failed request, output the error instead of failing the step.
  • timeout · number · Optional, Seconds to wait for a response. Empty: up to the flow limit (10 min).
  • followRedirects · boolean · Optional, Follow 3xx redirects instead of returning them as the response.

Triggers

New or Updated Contact · Poll

Triggers when a contact is created or updated in Microsoft 365 People.

Setup

Setup

  1. Add the Microsoft 365 People connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Cloud Environment (cloud), required.

OAuth scopes

  • Contacts.ReadWrite
  • offline_access
  • openid
  • email
  • profile
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-microsoft-365-people@0.3.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 7 actions and 1 trigger declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Microsoft 365 People connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-microsoft-365-people@0.3.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com