How to connect Process Street and Microsoft SharePoint Online
Create a New Scenario to Connect Process Street and Microsoft SharePoint Online
In the workspace, click the βCreate New Scenarioβ button.

Add the First Step
Add the first node β a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Process Street, triggered by another scenario, or executed manually (for testing purposes). In most cases, Process Street or Microsoft SharePoint Online will be your first step. To do this, click "Choose an app," find Process Street or Microsoft SharePoint Online, and select the appropriate trigger to start the scenario.

Add the Process Street Node
Select the Process Street node from the app selection panel on the right.


Process Street

Configure the Process Street
Click on the Process Street node to configure it. You can modify the Process Street URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Microsoft SharePoint Online Node
Next, click the plus (+) icon on the Process Street node, select Microsoft SharePoint Online from the list of available apps, and choose the action you need from the list of nodes within Microsoft SharePoint Online.


Process Street
β

Microsoft SharePoint Online


Authenticate Microsoft SharePoint Online
Now, click the Microsoft SharePoint Online node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Microsoft SharePoint Online settings. Authentication allows you to use Microsoft SharePoint Online through Latenode.
Configure the Process Street and Microsoft SharePoint Online Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Process Street and Microsoft SharePoint Online Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that donβt require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
β
AI Anthropic Claude 3
β

Microsoft SharePoint Online
Trigger on Webhook
β

Process Street
β
β
Iterator
β
Webhook response


Save and Activate the Scenario
After configuring Process Street, Microsoft SharePoint Online, and any additional nodes, donβt forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking βRun onceβ and triggering an event to check if the Process Street and Microsoft SharePoint Online integration works as expected. Depending on your setup, data should flow between Process Street and Microsoft SharePoint Online (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Process Street and Microsoft SharePoint Online
Process Street + Microsoft SharePoint Online + Slack: When a workflow run is completed in Process Street, the automation updates a SharePoint list and sends a notification to a Slack channel.
Microsoft SharePoint Online + Process Street + Microsoft Teams: When a new file is added to SharePoint, a Process Street workflow is initiated, and a notification is sent to a Microsoft Teams channel.
Process Street and Microsoft SharePoint Online integration alternatives

About Process Street
Use Process Street in Latenode to run repeatable tasks like onboarding or reports as part of larger workflows. Automatically trigger actions in other apps (CRM, databases) when checklist items are completed, keeping processes moving. This avoids manual updates and ensures audit trails, all at Latenode's execution-based pricing.
Related categories

About Microsoft SharePoint Online
Automate SharePoint Online document management using Latenode. Trigger flows on file changes, move documents based on content, or update metadata without code. Streamline approvals and notifications with visual workflows, integrating SharePoint with other apps. Benefit from flexible logic and scalable execution.
Similar apps
Related categories
See how Latenode works
FAQ Process Street and Microsoft SharePoint Online
How can I connect my Process Street account to Microsoft SharePoint Online using Latenode?
To connect your Process Street account to Microsoft SharePoint Online on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Process Street and click on "Connect".
- Authenticate your Process Street and Microsoft SharePoint Online accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically archive completed Process Street checklists to SharePoint?
Yes, you can! Latenode lets you automate archiving checklists. This ensures compliance and efficient document management within SharePoint using a no-code visual builder.
What types of tasks can I perform by integrating Process Street with Microsoft SharePoint Online?
Integrating Process Street with Microsoft SharePoint Online allows you to perform various tasks, including:
- Automatically creating a SharePoint folder when a Process Street checklist starts.
- Saving completed Process Street checklists as PDF documents in SharePoint.
- Updating SharePoint list items based on data from Process Street checklist responses.
- Triggering a Process Street checklist when a file is added to a SharePoint folder.
- Managing user access to SharePoint files based on Process Street checklist roles.
How easily can I customize integrations with JavaScript in Latenode?
Latenode allows you to seamlessly integrate JavaScript code for advanced data transformations and custom logic within your Process Street and Microsoft SharePoint Online workflows.
Are there any limitations to the Process Street and Microsoft SharePoint Online integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript knowledge.
- Real-time synchronization depends on the API limits of both platforms.
- Large file transfers can be affected by network bandwidth.