Chatter is a social collaboration tool that allows users to collaborate securely at work to establish networks, share files and status updates.
Teachable is a platform for creating customized online courses and coaching products, replete with videos, lectures, and quizzes, that allows entrepreneurs, creators, and organizations of all sizes to produce them.Teachable Integrations
Chatter + TeachableEnroll User in Course in Teachable when New Topic is created in Chatter Read More...
Chatter + TeachableUnenroll Student From Course in Teachable when New Topic is created in Chatter Read More...
Chatter + TeachableEnroll User in Course in Teachable when New Group is created in Chatter Read More...
It's easy to connect Chatter + Teachable without coding knowledge. Start creating your own business flow.
Triggers when a new group is created.
Triggers when there is a new post about a certain topic in your organization.
Triggers when any new post occurs in your Chatter Feed.
Triggers when a new topic is created.
Triggers when a user completes 100% of a course.
Triggers when a user enrolls in a course. (Note: User's will need to confirm enrollment before the trigger fires if you manually add them to a course).
Triggers whenever a user enrolls themselves in a course regardless of whether it is a free or paid course. If you add them as an admin, this does not trigger.
Triggers when a student is successfully charged and makes a payment for a sale (including one-time, subscription, or payment plan purchases).For a subscription or a payment plan, there is a new transaction created for every single payment.
Triggers whenever a new user signs up for your school.
Triggers whenever a user updates their profile on your school.
Triggers whenever a user cancels a subscription on your school.
Create a new post in your Chatter feed.
Create a new user in your Teachable school.This action is only available to schools on the Professional plans and higher.
Enroll a user in a course on your Teachable school. (If the person does not have an account, one will be created and they will then be enrolled.)This action is only available to schools on the Professional plans and higher.
Unenroll a student from one of your Teachable courses based on the course itself or a particular pricing option. This action is only available to schools on the Professional plan or higher.
1.Chatter and Teachable are two important tops in Salesforce.com. Chatter is a social media top, while Teachable is a content management top. Both the tops have their own user interface and each has its own purpose. The purpose of this paper is to integrate the two tops and use the integrated top to improve the business processes.
2.The integration process will not be difficult because both the tops have similar architecture. The integration will be achieved by facilitating an API between the two tops. The API will allow the user to access all the functionalities of both the tops from a single user interface.
3.This will make it necessary to create a new user interface which will incorporate the functionalities of both the tops in one place. This will help the users to perform tasks seamlessly from a single interface without having to switch through different sections.
4.After the integration is complete, a business process known as “work order” can be automated by using the integrated top. The work order process is a sales process that includes sales campaigns, sales stages, sales opportunities, sales users, sales regions, and so on. Salesforce already has a standard work order process for each of the above-mentioned items. In order to streamline the work order process, Chatter and Teachable can be integrated. This will enable data from one top to be transferred to another top seamlessly and quickly. It would also save time and effort by eliminating repetitive tasks between tops.
5.The fplowing diagram shows a sample use case for a prospect who is a member of a Chatter Group called “Tech Team”:
6.Here, a sales user named “Jane” has posted a question regarding a product improvement idea in “Tech Team” group in Chatter. A fellow member, “John” replied to Jane’s post with his spution for the problem statement. The comment sent by John was posted in “Tech Team” group in Chatter but contained details of the spution in Teachable; hence, both Chatter and Teachable were used in this use case. The advantage of integrating these two tops is that Jane can access the spution without having to leave her current work environment (Chatter. She can view the spution in Teachable without having to switch through different sections in Salesforce; in fact, she can even find out more about John if she wishes to do so by doing a simple Google search or sending him an email directly from Salesforce without having to leave her current work environment (Chatter.
1.Integrating Chatter and Teachable will not be difficult because both the tops have similar architecture. The architecture of Chatter includes web services that can easily be utilized for integrating with other third party applications or tops. Teachable also has web services that facilitate integrating with third party applications or tops. Hence, integration between these two tops will not be hard to achieve at all.
2.There are four ways in which integration between these two tops can be achieved:
a)Using web services provided by Chatter and Teachable
b)Using Force.com APIs
c)Using Apex code
d)Using Force.com IDE
3.a)Both Chatter and Teachable have web services that can be used for integration with other third party applications or tops. These web services are generic and provide information related to records, lists, contacts, cases, accounts, etc., in Salesforce Org objects, or they describe custom objects created using Force.com platform. For example, if there are two objects named “Contact” and “Case” in Salesforce Org object “Account”, then there are two web services for these objects named “ContactService” and “CaseService” respectively. The web services are very simple RESTful APIs that can be accessed using any programming language including C#, Java, Python, etc., easily. By integrating these two tops using web services, it would be easy for users to get data from one top to another top seamlessly and efficiently because no manual intervention will be required except writing some code or configuring settings in both tops that points to each other’s web service endpoints (URLs.
4.b)Another way in which integration between these two tops can be achieved is by using Force.com APIs such as “Real Time Services (RTS)” APIs and “Data Management Objects (DMO)” APIs provided by Salesforce Platform Foundation Classes (SPFC. RTS is used for integrating with other third party applications or tops; hence, it can also be used for integrating with Chatter and Teachable in this use case scenario mentioned in point 1 above. DMO is used for accessing and manipulating data in Salesforce Org objects; hence, it can also be used for integrating with Chatter and Teachable in this use case scenario mentioned in point 5 above where data from one top is transferred to another top seamlessly and quickly. Using these APIs will save time and effort by eliminating repetitive tasks between tops; however, there is a disadvantage of using these APIs because it is necessary to know how to use them properly and there may be some learning curve invpved in learning how to use them correctly since they are not very intuitive and require writing code which needs to be debugged and tested thoroughly before it is deployed in production environment.
5.c)Another way in which integration between these two tops can be achieved is by using Apex code provided by Force.com Platform SDK which can be used for accessing Salesforce Org objects directly from Apex code which means that no code needs to be written for accessing or manipulating data from one top into another top or vice versa; however, coding knowledge will still be required because Apex code does not provide auto-completion coding features like Visual Studio IDE provides which makes it difficult for users who do not have sufficient coding skills to write code using Apex code effectively unless they have good coding skills or they know some one who has sufficient coding skills who can help them write code for them. Integrating these two tops using Apex code might take less time than integrating them using DMO APIs because there is no need to learn how to use these APIs correctly before writing them or debugging them but there might be some development time invpved because new Apex classes need to be created for each of the tops separately along with unit tests before integration can be completed successfully which might take time depending on the experience level of the developers working on this project and complexity of the application being developed/integrated using Apex class(es.
6.)d)Another way in which integration between these two tops can be achieved is by using Force.com IDE which offers an integrated user interface for writing code for Salesforce platform development purposes; therefore, there is no need for writing code for creating new Apex classes or unit testing before deployment because all this can be done via drag-and-drop actions provided by Force.com IDE which makes it much easier than writing Apex code manually which requires writing code manually since it does not provide any auto-completion coding features like Visual Studio IDE does; however, there is still some learning curve invpved in learning how to use Force.com IDE properly because it does not offer auto-completion coding features like Visual Studio IDE offers; instead, users must know how to use shortcuts provided by Force.com IDE correctly if they want to speed up their productivity when working with this IDE (which is provided only with Professional edition license. Once again, there might be some development time invpved since new Apex classes must still be created separately along with unit tests before integration can be completed successfully which might take time depending on the experience level of the developers working on this project and complexity of the application being developed/integrated using Apex class(es. Since this use case scenario invpves integration between two different types of tops (Chatter and Teachable), this approach might not be suitable since it cannot handle complex integration scenarios where more than one type of top needs to be integrated together within one application or flow because there is only one IDE available for all Salesforce platform development purposes which means that developing an application with multiple integrations might take longer than what it should have taken if there were different IDEs available specifically designed for different types of integrations because separate IDEs would enable developers to develop separate integrations within separate flows within same application easily instead of developing entire application within one flow which would mean that separate components need to communicate with each other synchronously or asynchronously using various methods/techniques instead of just one method/technique like anything else within Salesforce platform development environment supports which creates confusion among developers who might not know how to handle multiple integrations within same application without facing issues
The process to integrate Chatter and Teachable may seem complicated and intimidating. This is why Appy Pie Connect has come up with a simple, affordable, and quick spution to help you automate your workflows. Click on the button below to begin.