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

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


Freshdesk

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


Freshdesk
⚙
Wachete

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

Freshdesk
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Freshdesk, Wachete, 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 Freshdesk and Wachete integration works as expected. Depending on your setup, data should flow between Freshdesk and Wachete (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Freshdesk and Wachete
Wachete + Freshdesk + Slack: When Wachete detects a new notification for a particular wachet (webpage change), find the associated Freshdesk ticket by ID and then send a Slack message to a public channel with details about the change and the ticket.
Wachete + Freshdesk + Google Sheets: Upon a new Wachete notification for a specific wachet, the flow finds the corresponding Freshdesk ticket using its ID and logs the Wachete webpage change details along with the Freshdesk ticket ID into a Google Sheet row for analysis.
Freshdesk and Wachete integration alternatives

About Freshdesk
Sync Freshdesk tickets with other apps in Latenode to automate support workflows. Update databases, trigger alerts, or generate reports based on ticket status, all without code. Connect Freshdesk to your CRM or marketing tools to close the loop on customer issues. Less manual work, more automation.
Related categories
About Wachete
Use Wachete in Latenode to monitor website changes and trigger automated actions. Get notified of price drops, content updates, or competitor activity, then use Latenode to update databases, send alerts, or adjust strategies – all visually. Automate critical responses faster than ever.
Related categories
See how Latenode works
FAQ Freshdesk and Wachete
How can I connect my Freshdesk account to Wachete using Latenode?
To connect your Freshdesk account to Wachete on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Freshdesk and click on "Connect".
- Authenticate your Freshdesk and Wachete accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I track Freshdesk ticket status changes via Wachete alerts?
Yes, you can! Latenode allows real-time monitoring of Freshdesk tickets, triggering Wachete alerts based on status changes. This ensures prompt awareness and faster response times.
What types of tasks can I perform by integrating Freshdesk with Wachete?
Integrating Freshdesk with Wachete allows you to perform various tasks, including:
- Automatically create Wachete alerts for high-priority Freshdesk tickets.
- Send Freshdesk updates to Wachete when monitored website content changes.
- Trigger Freshdesk ticket creation upon detecting critical Wachete alerts.
- Synchronize Freshdesk ticket data with Wachete monitoring parameters.
- Generate summarized reports combining Freshdesk data and Wachete findings.
How to automatically create Freshdesk tickets from Wachete alerts?
Use Latenode to watch Wachete alerts and create Freshdesk tickets. Customize alert conditions and ticket details for efficient automation.
Are there any limitations to the Freshdesk and Wachete integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- The number of API calls to Freshdesk and Wachete is subject to their respective rate limits.
- Complex data transformations may require JavaScript coding within Latenode.
- Historical data synchronization between Freshdesk and Wachete may require a custom setup.