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


Process Street
⚙
Awork

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

Process Street
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Process Street, Awork, 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 Awork integration works as expected. Depending on your setup, data should flow between Process Street and Awork (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 Awork
Process Street + Awork + Slack: When a checklist is completed in Process Street, a new task is created in Awork, and a message is sent to a Slack channel updating the team.
Awork + Process Street + Google Sheets: When time is logged on a task in Awork, a record is created in a Process Street data set, and the summary data is updated in Google Sheets.
Process Street and Awork 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 Awork
Manage Awork tasks in Latenode to automate project updates and reporting. Trigger flows on new tasks, sync deadlines across tools, or create custom reports. Use Latenode's logic functions and webhooks to connect Awork to any system, crafting automated workflows without complex coding, and scale project management tasks efficiently.
Related categories
See how Latenode works
FAQ Process Street and Awork
How can I connect my Process Street account to Awork using Latenode?
To connect your Process Street account to Awork 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 Awork accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger Awork tasks from Process Street checklist completions?
Yes, you can! Latenode allows triggering Awork tasks upon Process Street checklist completion. Automate project updates, saving time and improving team coordination.
What types of tasks can I perform by integrating Process Street with Awork?
Integrating Process Street with Awork allows you to perform various tasks, including:
- Automatically creating Awork tasks from completed Process Street checklists.
- Updating Awork project statuses based on Process Street workflow stages.
- Syncing client information between Process Street and Awork projects.
- Generating Process Street reports based on Awork task completion data.
- Sending notifications to team members when new tasks are created in Awork via Process Street.
HowsecureistheProcessStreetintegrationonLatenode?
Latenode uses secure authentication protocols and encrypts sensitive data, ensuring your Process Street and Awork data is protected during integration.
Are there any limitations to the Process Street and Awork integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Process Street workflows with extensive logic may require custom JavaScript code.
- Real-time updates are subject to API rate limits imposed by Process Street and Awork.
- Certain advanced Awork features might not have direct equivalents in Process Street and vice versa.