How to connect Process Street and Vitally
Create a New Scenario to Connect Process Street and Vitally
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 Vitally will be your first step. To do this, click "Choose an app," find Process Street or Vitally, 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 Vitally Node
Next, click the plus (+) icon on the Process Street node, select Vitally from the list of available apps, and choose the action you need from the list of nodes within Vitally.


Process Street
β
Vitally

Authenticate Vitally
Now, click the Vitally node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Vitally settings. Authentication allows you to use Vitally through Latenode.
Configure the Process Street and Vitally 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 Vitally 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
β
Vitally
Trigger on Webhook
β

Process Street
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring Process Street, Vitally, 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 Vitally integration works as expected. Depending on your setup, data should flow between Process Street and Vitally (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 Vitally
Process Street + Vitally + Slack: When a workflow run is completed in Process Street, this triggers an update to the customer's health score in Vitally, and then sends a notification to the CSM via Slack.
Vitally + Process Street + Jira: When a user's data is updated in Vitally (potentially decreasing their health score), a task is automatically created in Process Street for the CSM, and a bug is created in Jira for the engineering team.
Process Street and Vitally 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 Vitally
Use Vitally in Latenode to centralize customer success data and automate actions based on health scores. Sync data, trigger alerts for at-risk users, and personalize support workflows, all within Latenode's visual editor. Combine Vitally's insights with other tools for smarter, automated customer lifecycle management.
Similar apps
Related categories
See how Latenode works
FAQ Process Street and Vitally
How can I connect my Process Street account to Vitally using Latenode?
To connect your Process Street account to Vitally 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 Vitally accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update Vitally when a Process Street checklist is completed?
Yes, you can! With Latenode, trigger Vitally updates upon Process Street checklist completion, ensuring real-time customer data synchronization. Latenode's flexibility makes complex updates simple.
What types of tasks can I perform by integrating Process Street with Vitally?
Integrating Process Street with Vitally allows you to perform various tasks, including:
- Create a Vitally user when a new client onboarding Process Street checklist starts.
- Update a Vitally attribute when a specific task is completed in Process Street.
- Trigger a Vitally action when a Process Street checklist reaches a certain stage.
- Send a Slack message via Latenode upon Process Street checklist completion and Vitally update.
- Archive a Process Street checklist after successfully updating client data in Vitally.
How do I handle errors when Process Street fails to connect with Vitally?
Latenode provides robust error handling. Utilize its visual editor to define error paths and automated retry mechanisms, ensuring data integrity.
Are there any limitations to the Process Street and Vitally integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Rate limits imposed by Process Street and Vitally APIs may affect high-volume workflows.
- Complex data transformations might require JavaScript code blocks.
- Real-time data sync depends on the polling intervals of the respective APIs.