How to connect Acapela Cloud and Recut
Create a New Scenario to Connect Acapela Cloud and Recut
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 Acapela Cloud, triggered by another scenario, or executed manually (for testing purposes). In most cases, Acapela Cloud or Recut will be your first step. To do this, click "Choose an app," find Acapela Cloud or Recut, and select the appropriate trigger to start the scenario.

Add the Acapela Cloud Node
Select the Acapela Cloud node from the app selection panel on the right.

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

Acapela Cloud
⚙
Recut
Authenticate Recut
Now, click the Recut node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Recut settings. Authentication allows you to use Recut through Latenode.
Configure the Acapela Cloud and Recut 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 Acapela Cloud and Recut 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
⚙
Recut
Trigger on Webhook
⚙
Acapela Cloud
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Acapela Cloud, Recut, 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 Acapela Cloud and Recut integration works as expected. Depending on your setup, data should flow between Acapela Cloud and Recut (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Acapela Cloud and Recut
Acapela Cloud + Recut + Google Drive: When a new audio file is generated in Acapela Cloud, a video is created in Recut (assuming Recut can use the Acapela audio), and the resulting video file is then uploaded to a specified folder in Google Drive.
Acapela Cloud + Recut + YouTube: When an audio file is generated using Acapela Cloud, a video using that audio is created/edited in Recut. The video is then uploaded to YouTube.
Acapela Cloud and Recut integration alternatives
About Acapela Cloud
Need realistic voice synthesis? Integrate Acapela Cloud in Latenode to automate voice responses in your workflows. Generate audio from text for IVR systems, content creation, or accessibility features. Use Latenode's visual editor and JS node for full control over text prompts and delivery, scaling voice automation affordably.
Related categories
About Recut
Use Recut in Latenode to automate video editing. Automatically remove silences or unwanted sections from recordings, saving hours of manual work. Integrate Recut with other nodes to create automated content pipelines: generate clips, add captions, and post to social media. The Latenode visual editor makes it easy to build and scale complex workflows.
Related categories
See how Latenode works
FAQ Acapela Cloud and Recut
How can I connect my Acapela Cloud account to Recut using Latenode?
To connect your Acapela Cloud account to Recut on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Acapela Cloud and click on "Connect".
- Authenticate your Acapela Cloud and Recut accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically subtitle Recut videos with Acapela Cloud voices?
Yes, you can! Latenode’s visual editor lets you easily link Acapela Cloud’s voice generation to Recut, saving time and improving video accessibility with synchronized audio.
What types of tasks can I perform by integrating Acapela Cloud with Recut?
Integrating Acapela Cloud with Recut allows you to perform various tasks, including:
- Automating voiceover creation for Recut video projects directly from text inputs.
- Creating multilingual subtitles for videos using AI-powered Acapela Cloud voices.
- Dynamically generating and adding audio introductions or outros to Recut videos.
- Batch processing voiceovers for multiple Recut projects simultaneously.
- Syncing automatically generated speech with specific sections of video in Recut.
What Acapela Cloud featuresareaccessiblethroughLatenode?
Latenode gives you access to Acapela Cloud's voice selection, text-to-speech conversion, and audio customization options inside automated workflows.
Are there any limitations to the Acapela Cloud and Recut integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex audio editing within Recut might require manual adjustments post-automation.
- API rate limits for Acapela Cloud may affect the volume of voiceovers generated.
- Advanced Recut features may not be directly controllable through the integration.