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

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

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

Discourse
⚙
Recruitee
Authenticate Recruitee
Now, click the Recruitee node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Recruitee settings. Authentication allows you to use Recruitee through Latenode.
Configure the Discourse and Recruitee 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 Discourse and Recruitee 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
⚙
Recruitee
Trigger on Webhook
⚙
Discourse
⚙
⚙
Iterator
⚙
Webhook response
Save and Activate the Scenario
After configuring Discourse, Recruitee, 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 Discourse and Recruitee integration works as expected. Depending on your setup, data should flow between Discourse and Recruitee (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Discourse and Recruitee
Discourse + Recruitee + Slack: When a new topic is created in Discourse containing keywords related to job openings, the system searches for matching candidates in Recruitee. If candidates are found, a notification is sent to a designated Slack channel for HR.
Discourse + Gmail + Recruitee: When a new topic (blog post) is created in Discourse, the system sends an email to a predefined list of potential candidates found in Recruitee using Gmail.
Discourse and Recruitee integration alternatives
About Discourse
Integrate Discourse with Latenode to automate community management. Trigger actions based on new topics or replies. Automatically analyze sentiment, flag urgent issues, and update your CRM. Build custom moderation flows with Latenode's no-code tools, AI nodes, and flexible JavaScript functions, scaling support without manual effort.
Similar apps
Related categories
About Recruitee
Automate your hiring process with Recruitee in Latenode. Trigger workflows on new applications to screen candidates, send automated messages, and update other systems. Connect Recruitee to HR tools for seamless data flow and custom talent pipelines. Simplify recruiting tasks using Latenode's visual editor and scaling options.
Related categories
See how Latenode works
FAQ Discourse and Recruitee
How can I connect my Discourse account to Recruitee using Latenode?
To connect your Discourse account to Recruitee on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Discourse and click on "Connect".
- Authenticate your Discourse and Recruitee accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically announce new hires on Discourse?
Yes, you can! Latenode's visual editor allows you to trigger a Discourse post when a new candidate is hired in Recruitee, keeping your community informed and engaged, all with no code.
What types of tasks can I perform by integrating Discourse with Recruitee?
Integrating Discourse with Recruitee allows you to perform various tasks, including:
- Post new job openings from Recruitee to a dedicated Discourse channel.
- Create Discourse topics for candidate feedback from Recruitee users.
- Automatically update candidate profiles in Recruitee based on Discourse activity.
- Send welcome messages in Discourse to newly hired candidates from Recruitee.
- Trigger Recruitee actions based on keywords or sentiments in Discourse posts.
How can I use JavaScript for advanced Discourse/Recruitee integrations?
Latenode allows you to use JavaScript blocks to add custom logic and data transformations, going beyond basic no-code options for complex workflows.
Are there any limitations to the Discourse and Recruitee integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript knowledge.
- Rate limits of Discourse and Recruitee APIs may impact high-volume workflows.
- Custom fields in Recruitee may need specific mapping in Latenode.