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


Process Street
β

Sendy


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

Sendy
Trigger on Webhook
β

Process Street
β
β
Iterator
β
Webhook response


Save and Activate the Scenario
After configuring Process Street, Sendy, 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 Sendy integration works as expected. Depending on your setup, data should flow between Process Street and Sendy (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 Sendy
Process Street + Sendy + Slack: When a Process Street workflow run is completed, this automation triggers a marketing email to be sent via Sendy. A notification is then sent to a designated Slack channel to inform the team of the completed workflow and email send.
Sendy + Process Street + Google Sheets: When a new subscriber is added in Sendy, a new onboarding checklist is created in Process Street. Subsequently, the subscriber's data is added as a new row in a Google Sheet for record-keeping and analysis.
Process Street and Sendy 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 Sendy
Use Sendy in Latenode to automate email campaigns without complex coding. Trigger campaigns based on events in other apps (CRM, e-commerce). Latenode lets you process data, filter recipients, and personalize emails with JavaScript or AI nodes before sending via Sendy. Scale outreach efficiently and track results within your workflows.
Similar apps
Related categories
See how Latenode works
FAQ Process Street and Sendy
How can I connect my Process Street account to Sendy using Latenode?
To connect your Process Street account to Sendy 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 Sendy accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger email campaigns after task completion?
Yes, you can! Latenode's visual editor makes it easy to trigger Sendy campaigns when a Process Street task is completed, automating your follow-up process and improving efficiency.
What types of tasks can I perform by integrating Process Street with Sendy?
Integrating Process Street with Sendy allows you to perform various tasks, including:
- Automatically adding new Process Street users to a Sendy mailing list.
- Triggering personalized email sequences upon completion of specific checklists.
- Updating subscriber information in Sendy based on data from Process Street forms.
- Sending summary reports from Process Street as email campaigns via Sendy.
- Creating targeted email segments in Sendy using Process Street workflow data.
Can I use custom JavaScript to transform Process Street data?
Yes! Latenode allows you to use JavaScript code blocks to transform Process Street data before sending it to Sendy, unlocking advanced customization.
Are there any limitations to the Process Street and Sendy integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require some JavaScript coding knowledge.
- Rate limits on the Process Street and Sendy APIs can affect performance.
- Real-time synchronization depends on the polling interval configured in Latenode.