The Challenges of Managing Data in Process Street

Process Street’s Data Sets help centralize and reuse data across workflows. However, unlike dedicated databases, Data Sets have limitations that can slow teams down:

1. Manual updates are time-consuming: Keeping Data Sets current is tedious, especially for dynamic data like client lists, product catalogs, or team rosters.
2. Limited data validation: Data Sets don’t include advanced validation features, making it easier for errors like duplicates or inconsistent data to slip through.
3. No advanced queries: Data Sets offer basic filtering but lack the robust query tools found in most databases, which are often essential for managing and analyzing complex data structures.

Most Businesses Already Store Their Data Elsewhere

Most critical business data already lives in CRMs, ERPs, or databases. Managing it separately in Process Street creates duplication and inconsistencies. Integrating these sources eliminates manual syncing, ensuring workflows stay accurate and up to date.

The Solution: Dynamic Updates

By connecting Process Street to an external data source and automating updates, you can:

1. Keep Data Up to Date: Dropdowns automatically reflect the latest information, so you don’t have to update them manually.
2. Reduce Errors & Save Time: Dynamic dropdowns ensure accurate, pre-validated selections, making workflows more efficient.
3. Use Your Existing Tools More Effectively: Instead of manually copying data, integrate updates directly from your CRM or other systems.

Scale Without the Manual Effort

Managing large Data Sets manually becomes more challenging as your business grows. Automating updates keeps your workflows accurate while freeing your team to focus on more important tasks. With dynamic updates, dropdowns always reflect the latest data. No extra work is required.

By linking Process Street with external data sources, you combine easy-to-use workflows with powerful data management from your existing systems.

How to Dynamically Update a Data Set

This guide is for users who don’t use or have access to Zapier. I’ll be using Power Automate to send HTTP requests to Process Street’s API, but any tool that can send HTTP requests will work.

Efficient Data Set Syncing: A Smarter Approach

Below is my typical sync flow for creating, modifying, and deleting records in a Data Set. Every action first goes through the System of Record before updating the Data Set. While updating the Data Set directly from a Process Street Workflow Run might seem more efficient, this approach actually reduces the overall automation work required.
Instead of creating multiple automations, I build a single automation that monitors the System of Record for any new or modified records. When a change is detected, the automation locates the corresponding Data Set record and updates it accordingly. This streamlined method simplifies the process and ensures the Data Set stays in sync with your source of truth.

Step 1: Set Up Your External Data Source & Data Set

Start by defining how you want your data to be structured and managed. Consistency matters—without it, your external source and Process Street Data Set will fall out of sync.
Excel and Google Sheets work, but structured databases or tables are better. They enforce formatting and prevent accidental changes.

When setting up your Data Set, don’t sync everything. Only pull in what your workflow needs:

• Dropdown Field: The value displayed in the dropdown (e.g., client names, product SKUs).
• Row ID: The unique identifier from the source system (e.g., primary key, unique ID). This keeps records linked.
• Filter Fields: Extra fields to create filtered views (e.g., active vs. inactive items, categories).

For easier maintenance, keep column names similar between the external source and the Data Set. They don’t have to match exactly, but close alignment makes mapping and troubleshooting smoother.

Step 2: Connect the External Source to the Data Set

To keep your Process Street Data Set up-to-date, you can use webhooks to automate creating and updating records from your external source. Webhooks can create and update records, but they won’t delete them. For deletions, the Process Street API works, but Zapier makes it easier.
Here’s how to connect your external source to the Data Set:

1. Set Up a Webhook in the Process Street Data Set

Create a webhook in the automation settings of your Process Street Data Set. This webhook will receive data from the external source whenever a change occurs. The only configuration you’ll need to do will be when you send your first test data from Power Automate. Go ahead and copy the webhook’s URL and keep this window open so you can test the trigger later.

2. Create Your Syncing Automation

1. Open Power Automate and create a new flow.
2. Select a trigger that aligns with your external source (e.g., “When a row is added or modified” for databases or “When a file is updated” for Excel/Google Sheets).
3. Add an HTTP action to your flow and configure it as follows:
   1. Method: POST
   2. URI: Paste the Process Street webhook URL.
   3. Headers: Set Content-Type to application/json.
   4. Body: Format the payload with the data you want to send. For example:

{
“row_id”: “12345”,
“title”: “Example”,
“status_field”: “Active”
}

Use dynamic content in Power Automate to replace these placeholders with data from your external source.

3. Test the Power Automate Flow & Configure the Webhook

1. Run a test in Power Automate to confirm the data is hitting the Process Street webhook correctly.
2. Switch back to Process Street and click Test Trigger. This will bring in the data just sent by your flow test.
3. Configure the webhook. If everything’s set up right, the mapping will be a direct 1-to-1 from the JSON payload.

Process Street’s UI makes this part simple. If the data structure matches, it should work without issues.

Step 3: Manage Deletions Separately

Process Street webhooks won’t delete records, so you’ll need another approach to remove outdated entries:

• Process Street API: Programmatically delete records. This takes some technical know-how or an integration tool that can handle API calls.
• Manual Cleanups: Periodically review and remove outdated entries yourself.

I’m putting together a guide on setting up and automating row deletions with the Process Street API. It’ll walk you through using my filter query automation to pinpoint records for removal, making cleanup quick and painless. Stay tuned.

Keeping Your Data Set Accurate & Effortless

Webhooks keep your Process Street Data Set accurate—no manual updates, no errors. They handle updates, but deletions need Zapier or the API. With this setup, dropdowns stay current, workflows stay clean, and your team works with reliable data.

About the Author

Kai deSilva is The Creative Guy at Improvizations, a UKG-focused advisory and implementation firm expanding into AI-driven process consulting and optimization. With a background in graphic design and a passion for automation, Kai helps businesses—ranging from manufacturing and financial services to education and marketing—streamline workflows and enhance efficiency with AI. When he’s not optimizing processes, you’ll find him lifting weights, riding motorcycles, or exploring the intersection of creativity and tech.

The post Optimize Data Management with Data Set Automations first appeared on Process Street Help Center.

The Create Tasks via Email feature allows you to automatically create tasks in Process Street by simply sending an email. This is particularly useful for:

• Converting emails into actionable tasks without manual entry.
• Automating task creation from external systems that send email notifications.
• Forwarding important emails directly into Process Street as tasks.

How It Works

When enabled, Process Street generates a unique email address. Any email sent to this address creates a new task in “My Work.” The email subject becomes the task name, and the email body is added as the task description.

How to Enable “Create Tasks via Email”

1. Go to My Work in Process Street.
2. Click on the email icon () near the + Task button.
3. A pop-up window titled Create Tasks Via Email will appear.
4. Toggle the Enable create tasks via email switch to activate the feature.
5. Copy the unique email address displayed.
6. Use this email address to send or forward emails to create tasks.

How to Disable “Create Tasks via Email”

1. Open My Work in Process Street.
2. Click the email icon () again.
3. Toggle Enable create tasks via email off.
4. The feature will be disabled, and the email address will no longer accept task creation requests.

Best Practices & Tips

• Automation: Integrate this feature with tools like Zapier, Outlook, or Gmail filters to auto-send emails to the task email address.
• Consistency: Use structured email subjects for better task organization.
• Security: Share the email address only with trusted sources to prevent unwanted tasks.

This feature ensures that no important request or task slips through the cracks—try it today!

The post Create Tasks via Email first appeared on Process Street Help Center.

Whether calculating costs, extracting data, setting task priorities, or defining unique business logic, this feature is useful for performing complex operations beyond standard workflow automation.

You can use these tasks to perform multi-step calculations and make API calls to calculate data from another tool within your workflows. This reduces the need for reliance on third-party tools to perform calculations for you.

Users: In order to add or change Code Tasks in a workflow, you must be an Administrator or a  Member who has been given ‘edit’ access by your Administrator.

Code Task is automatically available on our Enterprise plan. Please contact our Support team or your Account Executive to inquire about access. 

Use case examples

Here are just a few examples of how you can utilize Code Tasks, but the limits are really your imagination!

Financial

• Credit Risk Assessment: Probability of Default (PD) × Loss Given Default (LGD) × Exposure at Default (EAD)
• Return on Investment (ROI): (Net Profit / Investment Cost) × 100
• Liquidity Ratios: Current Assets / Current Liabilities
• API call example: Fetching current currency conversion ratios or stock prices via API

Healthcare 

• Cost-Benefit Analysis for Medical Equipment: (Total Benefits of Equipment – Total Costs) / Total Costs
• Patient Risk Scoring: Likelihood of Readmission × Severity of Illness
• Healthcare Claims Processing:  Total Claims Submitted – (Denied Claims + Adjusted Claims)
• API call example: Submit the provided equipment order to a database API

Property Management 

• Rental Yield: (Annual Rental Income / Property Value) × 100
• Maintenance Cost Forecasting: Average Annual Maintenance Cost per Property × Number of Properties
• Depreciation Calculations: (Cost of Property – Salvage Value) / Useful Life
• API call example: Downloading regional property data from data provider API

Creating a Code Task

You can create Code Tasks in an existing workflow where you already have form fields created, or in a new workflow that you start from scratch.

If you’re starting from scratch, consider which input and output form fields you might want to include as part of your Code Task.

In your workflow click the + button at the end of the task list to add a Code Task.

Using a preset example

Click the dropdown shown in the image below to select a prebuilt function.

• Math formula – Calculate the total cost of a purchase
• Extract data – Extract domains from email addresses
• Unique ID generation – Generate a unique ID for records or tasks
• Currency conversion – Convert one currency to another
• Task priority – Set task priority based on the due date
• Risk assessment – Assign a risk score based on predefined criteria
• Process Street Public API call – Fetch data from Process Street’s API

Under the Input data section, click + Add value to add more input fields, or use the trash can to delete the ones you don’t need.

These values can be manually entered or pulled from previous workflow tasks as variables. A manually entered value for the API call would be your API key, for example.

Input form fields you can use are:

• Short text field
• Long text field
• Date field
• Number field
• Dropdown field
• Linked dropdowns (linked to Data Sets)
• Multi-choice field
• Hidden field

Output form fields you can use are:

• Short text field
• Long text field
• Number field
• Hidden field
• Send email widget

Note: In workflow view mode, other users won’t see API keys or other static values in your input fields unless they have edit permission on the workflow or they are an admin.

Generate code using AI

Click Generate with AI to let our Process AI wizard create the code for you.

Simply write a prompt and the Code Task looks at your existing input and output form fields and adds these in for you, ready for testing.

Create custom code

If you’re already familiar with JavaScript and don’t need presets or AI generation, you can write and execute fully custom JavaScript logic.

Input fields can be accessed by reading keys of the inputData variable and 0utput fields can be written by setting keys of the ouputData variable.

Example: The Code Task has an input called “Customer Name” and an output called “Address”. They can be accessed in the following way:

const customerName = inputData[“Customer Name”]
outputData[“Address”] = “599 Broadway, New York, 10012”

Test your Code Task

When you’re done setting up your inputs, outputs and code, you can go ahead and test it.

• Click Test in the top-right corner of your Code Task
• Enter test values in the input fields
• Click Run code to see the calculated results under Output data
• Validate your results by ensuring the calculations match expectations. Adjust the code or input variables if necessary

At this point you can go ahead and preview the Code Task in the editor, or publish it ready to be used.

Execution Constraints

• Execution Time Limit: 5 seconds maximum per execution
• Memory Limit: 128 MB maximum
• Throttling: There’s no special throttling or rate limiting
• Execution Environment: Runs on Node.js 22 within AWS Cloud
• Processing Limitations: Code execution is constrained by available resources and runtime limits to ensure consistent performance
• Time Handling: Code Task executions follow UTC timezone
• Javascript package imports: Not supported

Note: If you require longer than 5 seconds per execution, please contact our Support team or your Account Executive.

FAQ

What happens if my script exceeds the limits?

If a script exceeds execution time or memory limits, it will be terminated, and an error will be returned.

Can I make API calls within a Code Task?

Yes, but keep in mind the execution time limit (5 seconds) when making network requests.

What version of Node.js does Process Street use?

Code Tasks run on Node.js 22.

Are there any rate limits?

Currently, no rate limits apply.

Can I use third-party libraries?

At the moment, only native Javascript functions are supported – external libraries cannot be imported. See the list below for allowed globals.

How do I debug my Code Task?

Use the Test feature to run the code and review the output. Debugging logs can be added using console.log().

What timezone do Code Tasks use?

-All date/time operations in Code Tasks follow UTC timezone, regardless of account settings.

Where can I get support?

For advanced JavaScript issues, consult a developer.

Process Street provides support for how the Code Task processes code but does not debug user scripts.

Allowed globals for Code Tasks

All standard Javascript built-in objects are available (e.g. Math, Date, RegExp). Moreover, we have allowlisted the following Node.js globals:

“Blob”,
“Buffer”,
“console”,
“crypto”,
“fetch”,
“FormData”,
“Headers”,
“Request”,
“Response”,
“URL”,
“URLSearchParams”,
“clearInterval”,
“clearTimeout”,
“setInterval”,
“setTimeout”,
“structuredClone”

The post Code Task first appeared on Process Street Help Center.

Using Zapier to connect to other Applications and Automate your Processes

Zapier lets you automatically find and run your workflows in Process Street and trigger actions in over 5,000 apps, including Salesforce, Slack, Google Sheets, Asana, Airtable, and more.

Zapier is a service that connects your apps together so that you can automate tasks behind the scenes. For example, you could tell Zapier to create a new Process Street workflow run when a lead is added in Salesforce, send an email when a task is completed in Process Street or fill in contract variables in HelloSign and send the contract with data collected in Process Street.

This article covers:

1. How Zapier Works
2. Connecting your Process Street Account to Zapier
3. Setting up a Process Street Zap
4. Using Triggers to initiate Zaps
5. Using Find and Update
6. Ideas for Automations and Connections
7. Other Zapier Resources
8. Zapier Video Examples

1. How Zapier works

Zapier works by listening for events in one app, then automatically triggering an action in another. Essentially, it’s a cause-and-effect system of “if this happens, then do that”. At its most basic, if a task is completed in Process Street, then do [this action] in another application.

Process Street has a number of triggers, searches, and actions available through Zapier.

You can trigger an action in another application with these options:

• New Workflow Run
• When a Workflow run is completed
• New Task Checked
• When a Task is ready to be worked on
• New Comment Posted
• New Attachment Added to a Comment
• When a Record is added to a data set
• When a Record is updated in a data set
• When a Record is deleted from a data set

Search for a workflow run using:

• Find Workflow Run (by name or ID)

And create the following actions:

• Run Workflow if it doesn’t exist yet
• Run Workflow
• Update Workflow Run
• Update a Task in a workflow run
• Turn on the Workflow run share link automatically
• Add a new Record to a Data Set
• Create a Record in a Data Set
• Find a Record in a Data Set
• Update a Record in a Data Set
• Delete a Record in a Data Set

2. Connecting your account

To connect your Process Street organization to Zapier, you’ll want to generate and capture your organization’s API key here (must be Admin). If one has already been created, you can use that key for your integration.

Zapier will ask you for your API key the first time you connect your organization. When the window appears, copy the key you’ve just generated or that was previously generated for your organization.

3. Examples of Process Street zaps

The examples below are two basic examples and are just an introduction to what can be done. There are literally thousands of ways Process Street can interact with other software applications using Zapier.

4. Using Triggers to initiate zaps

You can easily trigger an action in another application using one of Process Street’s available triggers.

For this example, the zap created will send an email automatically in Gmail when a task is checked in a Process Street workflow run.

In your Zapier account, create a zap, choose Process Street as the trigger app and select ‘New task Checked’.

Select the workflow from Process Street that you want to use and the specific task you have chosen as the trigger. Zapier will attempt to pull sample data for you to review.*

*NOTE* For Zapier to successfully pull sample data, the action you are triggering must be completed. In this example, you are building a zap off of a task being checked off, so you must have an active workflow run with that task completed.

Tip: Put additional sample data inside of that workflow run. You can use it later on when building your email template.

When you are finished with setting up the Trigger, (the ‘if’ in ‘if this, then that’) select the application you want to take action in (the ‘then that’ part). In this case, choose Gmail and select ‘Send Email’ for the action. Learn more about using Gmail in Zapier.

Choose your recipients. You can use data from your workflow run sample here. For example, you can have the email sent to an email address entered in Process Street on a previous task.

Craft the body of your email and pull in any variables from your workflow run where needed.

Finally, test your zap, give it a name, and ensure it’s switched on. Done!

Tip: Place your own email in the ‘to’ field when testing. This will allow the test and sample to come straight to your email inbox.

5. Using find and update

The Find and Update option is used when you need to update an existing Process Street workflow run with new data. This allows you to “Find” an existing workflow run in Process Street by searching for it and then “Updating” fields on that run with new or updated information.

For this example, we’re going to update the ‘References’ fields in a workflow run when that information is added to a Google Sheet. When that spreadsheet is updated with new information, Zapier will search for the right workflow run in Process Street and pass the information.

To create this Zap, our Trigger application is Google Spreadsheet and A New or Updated Spreadsheet Row. Choose the right Spreadsheet and Worksheet in the next step.

For the second step of the zap, choose the Process Street app and the Find Workflow Run option. Next, choose the appropriate workflow.

When searching for a specific workflow run, you want to use data that will easily identify the workflow run you’re updating. Email addresses work great as they are unique to each workflow run.

After you’ve found your desired workflow run, add a 3rd step to your zap. This should be a Process Street action step. In this example, we want to use the ‘Update Workflow Run‘ action.

Select the same workflow that you have been building this zap for. Then, use a custom value for the workflow run ID. You can get the workflow run ID by clicking on the drop-down, choosing the find workflow run option, and then selecting ID.

Then, you’ll want to pull data into the fields you want to update. In this example, we are bringing in the new hire’s References from the updated Google sheet.

Finally, test your zap to be sure that it is pulling in the correct info from the updated spreadsheet and adding it to the right workflow run. Name your zap accordingly and ensure it is turned on.

Using the Find and Update function, the possibilities are truly endless. This can be used to update active workflow runs via a change in your CRM, spreadsheet, or action in Google Drive, Dropbox, HelloSign, etc. See our section on Ideas for Automations and Connections below, for other common uses of Find and Update for Process Street users.

6. Ideas for Automations and Connections

Using Process Street’s Zapier integration, the possibilities for integrations can be overwhelming. To get you started, here are a few of the most common uses we see among Process Street customers:

• Automatically send an email from Gmail (or any other email programs) when a task is checked
• Update Salesforce with data collected in a Process Street workflow run
• Run a workflow when something is done in Salesforce (and send in information from Salesforce to the workflow run)
• Fill out and send a contract via HelloSign using information collected in Process Street and a specific task is checked
• Add image files collected in a Workflow Run to a Dropbox (or Google Drive) folder

If you didn’t see one above that inspires you or you just love this stuff, we created an article with 50 Ideas for integrating Process Street via Zapier. You can check that out here.

7. Other Zapier Resources

Download our free eBook

We have created a 111-page ebook that explains how Zapier works and how you could use it with Process Street.

Click here to download the ebook

You can also read the chapters here:

Table of Contents:

• What Is Zapier? The Essential (Unknown) Time Saver
• Why Zapier is Your Dream Automation Software
• Zapier vs IFTTT: The Best Way to Automate Your Life?
• 222 Zaps to Crush Your Current Process Automation
• 50 Examples of Business Process Automation from the World’s Most Innovative Companies

50 Examples of how to connect Process Street with your other apps via Zapier

Zapier is most powerful when you get creative with the processes you want to automate, but to do that you need to have an idea of what it can do first.

Discover 50 more ways to integrate Process Street with your favorite apps

8. Zapier Video Examples

Zapier Form Integration Info: How to get your form-field data to and from applications (Process Street and Salesforce)

Example: An in-depth video showing how to push data from your CRM (Close.io) to Process Street, and back

Example: An in-depth video showing how to integrate Process Street, your CRM (Close.io) and a contract signing application (HelloSign)

The post Zapier (5,000+ Apps) + Process Street Integration first appeared on Process Street Help Center.

For example, an employee onboarding process could be scheduled to run on the date you’re onboarding your next new employee, whilst an office cleaning process could be set to run every day of the week, or an invoicing process could be scheduled to run every month for each of your clients.

Users: To be able to schedule a Workflow run you must be an Admin or a Member with either “Edit”, “View All” or “Run” permissions.  

How to schedule a Workflow run

There are two ways you can schedule a Workflow run; from your library or from a Workflow’s menu.

From your Library

Click “Library” at the top of your screen and then click “Scheduled” on the left side of your screen, as shown below.

If you’ve not scheduled any Workflow runs before, you’ll be prompted to do this by clicking the button in the center of your screen.

If you already have a schedule set up you can click the “+ Schedule Workflow” in the top right corner, as shown below.

Note: To manage scheduled Workflow runs once they have been set up, click one of the run names in the list to open up the schedule to change, copy, or delete it.

From the workflow dashboard

You can schedule a workflow while you’re viewing its dashboard by clicking Schedule runs in the right panel, as shown below.

From the workflow editor

You can also schedule workflows to run as you’re editing them.

Navigate to the workflow you want to schedule and click Triggers or the + icon above your task list, then select Schedule to open the scheduling tool where you can make your selections.

Scheduling options

Once you have opened the schedule settings, you can set all the options for your scheduled or recurring Workflow run.

Here are the options you are presented with, in order from top to bottom:

Workflow

You can choose any workflow in your organization to schedule. Click on the dropdown to search through them.

Workflows will appear in alphabetical order which you can scroll through, or you can type a workflow name in the search box to narrow down your choice.

This is a required field, so you must select a workflow to be able to schedule a workflow run.

Name

The name field lets you set the name for your scheduled workflow run.

You can use variables such as “{{workflow.name}}” and “{{current_date.full}}” to include the date and time the workflow was run in the title, respectively. Keep or delete these fields as required.

Assignees

You can assign whoever you need (yourself, Members or groups) to be automatically assigned to a scheduled workflow once it has run.

Note: Only Members of your organization can be assigned to a scheduled workflow run. Guests (Internal) and Guests (External) cannot be assigned here.

Click “Assign members” and select the user or group you want to assign from the dropdown menu. You can also type their name in the search box to help narrow down your search.

Anyone assigned to a scheduled Workflow run (including yourself) will receive an email notification when the Workflow is run. Learn more about using email notifications.

Repeats

The “Repeats” dropdown menu will let you select how often your Workflow will be run.

• “Nope” means that your Workflow run will not be repeated – it will only run once, at the date and time you select, for example at the date and time of an upcoming meeting
• “Yearly” runs your Workflow every set number of years, which you can select in the “Repeats every” field. You can choose every year, every two years, every three years and so on
• “Monthly” will schedule your Workflow to run every set number of months, which you can set in the “Repeat every” field. You can also choose to repeat on either the same day of the month as the first or the same day of the week. You can also set Workflows to run quarterly or bi-yearly
• “Weekly” lets you select one or more days of the week the Workflow will run, and how many weeks between each set. For example, every 2 weeks on Monday and Friday
• “Daily” runs your Workflow every set number of days, for example every 2 days. You can also set the days of the week that the Workflow will run on

Timezone

The timezone dropdown field lets you select the timezone your workflow run will be based on. For example, if one of your team works in a different timezone to you, you can schedule your workflow to run for them in their own timezone.

Type the city in the timezone search box to help narrow down the timezone you want to choose.

Note: You can set your personal timezone in your profile and settings page.

Start date

The start date is a required field and it’s where you can select the date and time that your first scheduled workflow will be run on.

Remember that this will influence the day or date your workflow run recurs if you use a repeating schedule.

Click “Set date” to open up the date picker. Set the date and time required and then click “Save” to finish.

Note: You can only schedule workflows to run on future dates and times.

Due after

The “Due after / Set offsets” field lets you select when your scheduled workflow runs will be due. This effectively gives your workflow run a deadline to be completed.

Click “Set offsets” to be able to make your selections, which are automatically saved.

This Due After date is based on when your workflow is run, so for example, a 7-day offset sets the due date to be one week after the workflow is run, as shown in the example above.

If the workflow your scheduling has a default Workflow Run Due Date, this Due After date will override the default date. However, if you don’t specify a Due After date, your scheduled workflow run will be due as set by default.

Click “Remove” if you’d like to delete your due date offset.

Summary

Once all your options are chosen, read the summary at the bottom to double-check that your settings are correct.

Save your schedule

If you’re happy to save this schedule, click the “Schedule” button at the bottom of your screen to finish.

Note: You will only see a workflow run from the scheduler in My Work (and any tasks that have been assigned to you within it) once the workflow has been run.

Managing scheduled Workflow runs

To manage your scheduled workflow runs click the “Scheduled” button in the left-hand menu in your Library.

From here you can update or change settings to a schedule, copy a scheduled workflow run, or delete a scheduled workflow run.

Update an existing schedule

To update or change the settings of an existing schedule, start by clicking on the run name in the list to open up the settings menu.

Make the changes you want to make and when finished, click the “Update” button at the bottom of the page to save your changes.

Note: When you update a recurring workflow run, this will update all future workflow runs created from this schedule, but not existing ones that have already been run.

Copy an existing schedule

You can run a scheduled Workflow at different dates and times (or for different team members) from the same workflow by copying a schedule.

Start by clicking on the run name to open up your scheduled workflow run so that you can see the settings.

Click “Copy” at the bottom of your screen, make your selections for the copy, and click “Schedule” to save your selection.

Delete a scheduled workflow run

If you no longer need the schedule to run, you can delete it.

Click on the run name to open the schedule for that workflow run, and click the “Delete” button at the bottom of the page.

Note: Deleting a recurring workflow run will prevent any future workflow runs from being created via the scheduler, but this action will not affect your workflow or any active workflow runs you already have created.

The post Scheduled Workflow Runs first appeared on Process Street Help Center.

Since there are around 500 connectors with multiple triggers and actions, what you create in a Power Automate is really up to your imagination.

Create simple two-step or three-step flows, or get fancy with multiple steps, multiple tools, branching paths, variables and increments. The choice is yours!

Users: In order to create a Power Automate connector or an API key, you must be an Administrator. 

This article covers:

• How Power Automate works
• Creating and testing an automated cloud flow with Process Street’s connector
• Ideas and suggestions for flows
• More Power Automate resources

How Power Automate works

Power Automate uses a series of triggers and actions to automate your work. A trigger is something that starts a flow and an action is something that happens once the flow has been triggered.

Process Street triggers

• When a workflow run is created:
  • The automation will fire each time that a workflow run is created in Process Street
• When a workflow run is completed:
  • The automation will fire each time that a workflow run is completed in Process Street. This can be workflow runs from a selected workflow, or for all workflows
• When a task changes status:
  • The automation will fire each time a task in Process Street is either completed, uncompleted or both (i.e. unchecked might be either manually unchecked or when an approval task has been rejected).
  • When a task is ready: The automation will fire for each task that is not stopped and not hidden when a workflow is run.
    I.e. when a task is shown by conditional logic, is released by a stop task, or when a task has been submitted for approval.

Process Street actions

• Get a user:
  • Find a user’s name and email address by using the “Created by ID” or “Updated by ID” dynamic fields
• Find workflow runs:
  • Returns your latest 200 active workflow runs, showing the most recently updated first. You can search runs by data collected in form fields and system fields
• Get workflow run form fields:
  • Fetch a batch of form field values for a workflow run. Form field values are paged, meaning the links section in the response must be used to get the next/previous batch of form field values
• Run a workflow:
  • Creates a workflow run by selecting a workflow by name or ID
• Update a workflow run:
  • Updates a workflow run’s name, due date, status (active, archived, completed, deleted)
  • Automatically tun on the share link – Set the shared status to either Yes/No
• Update workflow run form fields:
  • Allows updating form field values in a workflow run. A value may consist of a simple string, may accept multiple values as an array, or may accept multiple properties
  • For task assignments, you can update the members form field or an email form field, to set role assignments on tasks

1. Create an automated cloud flow

Login to Power Automate or create an account if you don’t already have one.

On the left-hand menu, click Create and then select Automated cloud flow.

In the next screen, add a name for your flow and select a trigger. You can type Process Street to view the triggers available.

Note: This is if you’d like something happening in Process Street to happen before you add an action. (At this point, you could add another connector from another app as your trigger and have an action in Process Street as the next step if you prefer).

Once you’ve chosen a trigger, click Create.

If you’re not sure what trigger to use for now, click Skip.

2. Generate your Process Street API key

Once you have selected a Process Street trigger, you’ll be prompted to add your API key (if you’ve already added your API you won’t see this step).

You can generate and name a new API key from the integrations page in your Process Street organization manager area (for admins only).

The name of your API key will show in notification emails sent to users you have provisioned, so it’s best practice to change the default label (API Key #1) to avoid confusion (e.g. you can name it Power Automate, or anything else you’d prefer).

Add a name for your connection (e.g. your organization name) and add your API key. Click Create to continue.

Next, let’s take a look at creating an example flow.

Use case: A property management company wants to send one of their tenants a lease renewal workflow run to complete. The property manager checks a task as complete in the run, which triggers Power Automate to turn on the run share link and email a link to the run to the tenant.

We’re going to use four steps to create this flow:

1. Trigger: When a task is checked, unchecked or ready
2. Action: Update a Workflow Run
3. Action: Get workflow run form fields
4. Action: Send an email via Gmail

3. Set up your trigger

Select the trigger When a task is checked, unchecked, or ready.

In the task state field, select Task Checked.

Next, select your workflow by name (or ID). (If you leave the workflow ID field blank, this will trigger for all workflows in your organization).

Note: You can only search for workflows in your organization library, not those that have been created in your private library.

Next, select the specific task you’d like to trigger your flow. If you don’t specify a task it will work when any tasks in that workflow run are completed.

Click New Step to add more steps to your flow.

4. Set up your first action

Choose the action Update a workflow run.

Click the field for Workflow Run ID and search for runID in the dynamic content modal. Select WorkflowRunID, as shown below.

Next, since we don’t want to change the name, status or due date for the workflow run, we’re going to choose the name for this workflow run from the dynamic content, select Active as the status and select the due date from the dynamic content.

Optional: If you’d like to give your new workflow run a different due date, use the following date formatting: YYYY-MM-DDTHH:mm:ss. For example: 2022-07-10T15:00:00.00.

Click the shared field and select Yes to automatically turn on the share link for the workflow run.

5. Set up your third action

Click New Step to add the third step to your flow.

Choose the action Get workflow run form fields. Select the dynamic workflow run ID, the workflow and then the task that your email field is in.

Click New Step to add the final step to your flow.

6. Set up your fourth action

In this example we’re going to send an email via Gmail to our tenant. We can use the dynamic field for Tenant email address that we have set up in our Process Street workflow.

Click Add dynamic content to search for the email field.

Add a link to your workflow run into the body from the dynamic fields. Type URL in the search field to find it quickly.

In the subject and the body of the email, you can choose more dynamic fields and add any attachments you might need to send.

Your flow set up is complete! Click Save, then click Test in the top right corner of your screen.

Manually test the flow. Head to a test workflow run in Process Street and check off the task that you’ve set up as the trigger.

Once you’re done testing, you’ll see a banner message like this to confirm you’re good to go.

Ideas and suggestions for flows

There are literally thousands of ways that you can create flows to streamline your business operations. Here are a few suggestions to help you get started:

• Run a Support workflow when you receive a new ticket from a customer in Intercom
• Update a workflow run form fields with new opportunity details in Salesforce
• Create a Microsoft Teams chat from an email notification from Process Street
• Discover premade flow templates that you can add the Process Street connector into

More Power Automate resources

• Getting started with Power Automate
• Working with dates, times & timezones inside of your flows
• Monitoring a source for new or updated items
• Schedule flows to run on a recurring or one-off basis
• Update a list of items at once with apply to each
• Add delays into your flows
• Add conditional logic steps into your flows
• Parse data, create filter arrays and tables with data operations
• Use variables to count, increment or decrement data

The post Microsoft Power Automate first appeared on Process Street Help Center.

Users: To sync tasks, you must be an Admin or a Member with permission to Edit workflows.

For example, by syncing your Process Street tasks, you can automatically update them when you do any of the following actions in Asana:

• Complete a task
• Add an attachment to a task
• Add a comment in a task
• Update a task

You can check the complete list of Asana’s triggers in Zapier.

Preparations in Process Street

To sync your tasks, first, you need to create a workflow with some form fields.

If this is your first workflow, follow the detailed steps here to create your workflow. If you have an existing workflow that you want to work with, you can do that too.

Preparations in Asana

Log in to your Asana account or create one. Go to the project you want to use for this integration and ensure you have a few tasks created.

If this is your first project, refer to Asana’s guide on creating a project.

Create a zap

To sync your tasks between Process Street and Asana, you need to create a zap that will automatically complete tasks in your Process Street workflow runs when you update tasks in Asana.

Log in to your Zapier account or create a new one.

Click the + Create button and click Create zap. Select the Trigger as Asana and select Action as Process Street, as shown below.

Setting up the Trigger

Once you’ve selected Asana as your Trigger, select the Event as Updated Task. You can also go through the remaining options and choose what suits you best.

Proceed to connect your Asana account with Zapier. You can learn how to do that here.

Then select your Workspace and Project, as shown below.

To ensure you have connected the right account and chosen the right project, test your connection. For your test to return successful, you must have at least one task in your project that you have added or updated recently.

Setting up the Action

Before we set up the action of updating a task in a workflow run, we need to first find the related workflow run.

To do this, once you select the Action as Process Street, select the Event as Find Workflow Run in Process Street.

Connect your Process Street account with Zapier using an API key. You can learn how to do that here.

Then select the workflow you want to update. To ensure you find a workflow run relevant to the task you want to update, select the workflow run name using the task name in Asana, as shown below.

Then test your step. To make sure your test returns successful, you must have at least one active workflow run for that workflow, preferably with the same name as you selected.

To set up the action of updating a task in the workflow run you just found in your zap, click the + button below this step to add another action. Select Process Street as the App and select Update Task as the Event.

To connect your Process Street account, select the same one you connected in the previous step and then select the workflow you selected in the previous step.

For the workflow run, look for ID from the previous action where you found an active workflow run. Then select the task that you want to update and select the task status as Completed, as shown below.

Test your step to ensure the task you selected is marked as complete. For your test to return as successful, the task you want to update via Zapier must be actionable. This means it should not be blocked by an approval or a stop task before it or any required fields within it.

As an extra step to ensure your zap works as expected, go to Asana and update a task’s status. Then go to the relevant workflow run in Process Street. The task you selected while creating your zap should be marked as completed automatically, as shown below.

If you face any issues while creating this zap, please reach out to our support team.

You can also create and manage all the tasks you need, within Process Street.

Learn more about all the automations you can create with Process Street.

The post How to Sync Tasks between Asana and Process Street first appeared on Process Street Help Center.

You can integrate Google Calendar with Process Street workflow runs using Zapier.

Data you capture in your workflow runs can be used to automatically create events in Google Calendar. That means you can record information as you work through your tasks, and then automatically create and/or edit events to keep your schedule up to date.

If you’d like to know more about automating your processes in general, check out our free business process automation guide.

Use case:

• A company manages their Customer onboarding process with Process Street
• The company wants to automatically create an event in Google Calendar to log the time of the initial meeting with the client

Users: To create an API key for integrations, you must be an Administrator.

Process overview:

• Create a workflow in Process Street with the relevant form fields required for this integration
• Set up your calendar in Google Calendar
• Create a Zap in Zapier to create a new event in Google Calendar when you check off a task in a Process Street workflow run
• Configure the Zap to pull information from the Process Street form fields and use it to populate the new event with extra information

Let’s get this set up!

Add form fields to your Process Street workflow

First, add form fields to your customer onboarding workflow in Process Street. These can be used to record data when working through the tasks, which you will later push into Google Calendar as a new event.

You can add form fields while editing a workflow.

In this case, we’ve set up form fields to capture the following information:

• Client name
• Client email
• Client company name
• Initial meeting date
• Initial meeting agenda

Add form fields to your workflow to let the person working through it record important information (such as the elements above). Think of everything you’d like to transfer to your Google Calendar and add a form field for each one to be captured.

After that, it’s time to make sure that your calendar is set up and ready for the information to be pushed through.

Set up your calendar in Google Calendar

Next, ensure that your calendar in Google Calendar is set up and ready for the information captured in your workflow runs to be pushed through.

There’s not much to this step, other than that you need to have an account set up and (depending on your preference) have a separate calendar in place to track your client meetings.

If you have a Google account then it’s as simple as logging into the Google Calendar site with it.

Create a Zap in Zapier

This allows you to create a new event in Google Calendar when a task is completed in your Process Street workflow run.

Zapier is a tool that connects over 6,000 different apps. Any action in the supported apps (like forwarding an email or adding an attachment to a task) can be set up to trigger another app’s features automatically. Zapier integrates with both Google Calendar and Process Street. The whole recipe (Trigger + Action) is called a Zap.

Log into Zapier or create an account, then click “Create Zap“.

In your new Zap, select Process Street as the trigger app and select “New Task Checked” as the trigger.

Click “Continue” and connect your Process Street account.

Next, move on to set up your trigger. Choose the workflow and the task that you are using as the trigger for your zap.

Before you go on to test your trigger in Zapier, make sure you’ve run your workflow, filled in the required form fields, and checked off the task that you’ve asked Zapier to detect. This way, Zapier has some sample data to pull in and validate.

Click “Continue“, test your trigger and you should see a successful set of sample data has been pulled into your zap.

Congratulations! You’ve just set up Process Street as your Trigger for the Zap. Next, it’s time to set up Google Calendar as the place where your Action will take place.

Create your action step

Next, configure your Zap to push information into the event from your workflow run.

Choose Google Calendar as your app and “Create Detailed Event” as the action. This tells Zapier to create an event in Google Calendar when the task you previously selected in your Process Street workflow run is checked off.

Connect your Google Calendar account and then move on to setting up the event that will be created. The only required elements you need to fill in are the calendar you want to use and the start and end date of the event.

Now, you want the start date of the event to be the value recorded as your “Initial meeting date” in the customer onboarding workflow. To do this, you have to push the information into Zapier as a custom value in the “Start Date & Time” field.

For the end date, you’ll also want to add a “+Xh” after the form field data (with a space between them), where X is the number of hours you want the initial meeting to take.

In the same manner, you can also link the following data:

• The event “Summary” to be “Customer onboarding”, then the client’s name and company name
• The event “Description” to be the “Initial Meeting Agenda”
• The “Attendees” to include the client’s email address

Once you have your Zap set up, continue through to the test phase.

Finally, head over to your Google Calendar to make sure that your event has been created.

Once that’s done, name and turn on your Zap, then test it out again by running your workflow, completing the required form fields, and ticking off your Trigger task. Make sure that the event is created correctly with all of the relevant information in the right place.

And there you have it! Here’s to saving time and energy that’s better spent on your more important tasks.

The post Google Calendar + Process Street Integration first appeared on Process Street Help Center.

Users: To sync tasks, you must be an Admin or a Member with permission to Edit workflows.

For example, by syncing your Process Street tasks, you can automatically update them when you:

• Update a database item in Notion
• Complete a task in Asana
• Change column values in Monday
• Update an issue in Jira

Preparations in Process Street

In order to sync your tasks, you first need to create a workflow. To do this, go to your Process Street library or go into a folder and click the + New button in the top right corner. Select Workflow and click Start a Blank Workflow.

Give your workflow a name and add tasks to the left. If this is your first workflow, follow the detailed steps here to create your workflow.

If you have an existing workflow that you want to work with, you can do that too.

Preparations in Monday

For this example, we’re working with monday.com.

Log in to your Monday account or create one. Click the + button in the left panel to add a new item to your workspace and select New board.

Give your new board a name and manage your tasks, as shown below.

Create a zap

To sync your tasks between Process Street and Monday, you need to create a zap that will automatically complete tasks in your Process Street workflow runs when you update tasks in Monday.

Log in to your Zapier account or create a new one. Click the + Create button and click Create zap.

Select the Trigger as Monday or the app you’re working with and select the Action as Process Street, as shown below.

Setting up the Trigger

Once you’ve selected Monday as your Trigger, select the Event as Specific Column Value Changed in Board. You can also go through the rest of the options and select what suits you best.

Proceed to connect your monday.com account using an API token. You can learn how to do that here.

Then select your Board ID and Column ID, as shown below.

Then test your connection. To make sure your test returns successful, you must have at least one task in your board in Monday.

Setting up the Action

Before we set up the actual action of updating a task in a workflow run, we need to first find a workflow run.

To do this, once you select the Action as Process Street, select the Event as Find Workflow Run in Process Street.

Connect your Process Street account with Zapier using an API key. You can learn how to do that here.

Then select the workflow that you want to update. To ensure that you find a workflow run relevant to the task you update, select the workflow run name using the task name in Monday, as shown below.

Then test your step. To make sure your test returns successful, you must have at least one active workflow run for that workflow.

To set up the action to update a task in the workflow you just found in your zap, click the + button below this step to add another action. Select Process Street as the App and select Update Task as the Event.

To connect your Process Street account, select the same one you connected in the previous step and then select the workflow that you selected in the previous step.

For the workflow run, look for ID from the previous action where you found an active workflow run. Then select the task that you want to update and select the task status as Completed, as shown below.

Then test your step. To ensure your test returns as successful, the task that you want to update via Zapier must be actionable. This means it should not be blocked by an approval or a stop task before it or any required fields within it.

As an extra step to ensure that your zap works as expected, go to Monday and update a task’s status. Then go to the relevant workflow run in Process Street. The task you selected while creating your zap should be marked as completed automatically, as shown below.

If you face any issues while creating this zap, please reach out to our support team.

You can also create and manage all the tasks you need, within Process Street.

Learn more about all the automations you can create with Process Street.

The post How to Sync Tasks between Monday and Process Street first appeared on Process Street Help Center.

You can use outgoing webhooks to keep your other tools notified about the status of a workflow run or task in Process Street, or use incoming webhooks (webhook triggers) to run a workflow automatically when something happens in another app.

Users: You must be an Administrator or a Member with edit permissions in order to set up Webhook Triggers. 

Webhook Triggers

You can use Process Street’s webhook triggers to listen for event-driven triggers in other apps, to run a workflow in Process Street.

For example, run a workflow when a candidate is marked as hired in People HR, when supplier details change in Hubspot or when a new task is added in Asana.

Check your form fields

Be sure to have form fields set up and ready to capture data from your webhook trigger. For example, Employee First name, Employee Last name, Date of contract, Salary etc.

Setting up a Webhook Trigger

Start by editing the workflow you’d like to set up the webhook trigger on.

Click Triggers to open the setup modal, as shown below.

Search for the app you’d like to connect to and give it a name.

Note: You can also set up a custom webhook for any app you’d like. Type webhook into the search box to set this up.

For additional guidance, each of the apps has a link to a help document for webhooks inside the set-up modal.

Note: If your app gives you options for payload content type, be sure to select JSON format.

Click to Copy your webhook URL.

Next, select the event you’d like to use as the trigger. Some apps only have one option, in which case, select default as shown above.

Click See Payload to check what data comes in from your chosen webhook.

Now you can map the fields from the webhook to form fields in your workflow. The webhook fields are automatically created for you. All you need to do is map them to your Process Street form fields.

When you’re done mapping fields, turn on the webhook with the toggle switch and click Save to finish.

Now each time the event occurs in your other app, a workflow will be run in Process Street.

IP addresses used

There is no specific IP address used when sending webhooks, but it will always be an AWS IP address.

Webhook Trigger FAQ’s

Why isn’t my workflow running?

You may not have completed the setup for the webhook. If you see an orange warning sign like the one below, click the app’s name to complete the setup. Turn on the trigger and click Save to finish setting it up.

I don’t see the app I want to use in the list

We will be adding more apps to the list over time, but please contact our support team to request the app you’d like to use. Alternatively, you can use the other third-party tools shown in the setup modal to run your workflow.

The post Webhook Triggers first appeared on Process Street Help Center.