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

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

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

Close CRM
âš™
Teachable
Authenticate Teachable
Now, click the Teachable node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Teachable settings. Authentication allows you to use Teachable through Latenode.
Configure the Close CRM and Teachable 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 Close CRM and Teachable 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
âš™
Teachable
Trigger on Webhook
âš™
Close CRM
âš™
âš™
Iterator
âš™
Webhook response
Save and Activate the Scenario
After configuring Close CRM, Teachable, 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 Close CRM and Teachable integration works as expected. Depending on your setup, data should flow between Close CRM and Teachable (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Close CRM and Teachable
Close CRM + Teachable + Slack: When a lead's status changes in Close CRM to 'Closed Won', automatically enroll the lead (now a customer) in a specified Teachable course and notify the sales team in a designated Slack channel.
Teachable + Close CRM + Gmail: When a student completes a Teachable course, update their corresponding lead record in Close CRM to reflect their course completion and send them a personalized congratulatory email through Gmail.
Close CRM and Teachable integration alternatives
About Close CRM
Automate Close CRM tasks in Latenode to streamline sales processes. Automatically update deals, create tasks, or trigger follow-ups based on custom events. Integrate Close CRM with other apps like Slack or Google Sheets to centralize your data and communication flows using Latenode’s visual editor and flexible logic.
Similar apps
Related categories
About Teachable
Automate Teachable course management in Latenode. Enroll students, track progress, and send targeted communications based on course activity. Integrate with CRMs or marketing platforms for personalized learning paths. Use Latenode’s visual editor and flexible nodes for streamlined student lifecycle automation.
Related categories
See how Latenode works
FAQ Close CRM and Teachable
How can I connect my Close CRM account to Teachable using Latenode?
To connect your Close CRM account to Teachable on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Close CRM and click on "Connect".
- Authenticate your Close CRM and Teachable accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically create Close CRM leads from new Teachable students?
Yes, you can! Latenode automates lead creation, saving sales time. Trigger workflows based on new Teachable enrollments to instantly populate Close CRM with qualified leads.
What types of tasks can I perform by integrating Close CRM with Teachable?
Integrating Close CRM with Teachable allows you to perform various tasks, including:
- Create new Close CRM leads from new Teachable student enrollments.
- Update Close CRM lead status based on Teachable course completion.
- Send personalized email sequences via Close CRM for specific Teachable courses.
- Add Teachable students to Close CRM segments for targeted outreach.
- Trigger Close CRM tasks for sales reps based on Teachable student activity.
How secure is my Close CRM data when using Latenode integrations?
Latenode employs advanced encryption and secure authentication protocols to protect your Close CRM and Teachable data during all integrations.
Are there any limitations to the Close CRM and Teachable integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex custom fields in Close CRM may require JavaScript for full compatibility.
- Teachable API rate limits may affect high-volume data processing.
- Historical data migration might require manual configuration due to API constraints.