Integrating related third-party services for user interaction
Disclosed are various approaches for connecting third-party services for user interaction. An integration service can receive from a client device a content query including a selection of content by a user interacting with a user interface on the client device. The integration service can compare the content query with predefined connector data to identify a connector associated with the content query. The integration service can send the content query and an authentication token of the user to the connector to access information from a third-party service. In response to receiving the information from the third-party service, the integration service can provide the information to the client device.
1. A system for integrating related third-party services for user interaction, the system comprising:
at least one computing device;
at least one application executable in the at least one computing device, wherein, when executed, the at least one application causes the at least one computing device to at least:
receive, over a network, a query from a client application executing on a client device, the query comprising a selection of content from a user interface of the client application;
identify a particular connector associated with the query from a plurality of connectors by comparing the query with connector data, the connector data comprising at least one of a keyword or a structure being mapped to a respective connector of the plurality of connectors, the plurality of connectors being associated with a plurality of third-party services, and the particular connector providing access to a particular third-party service of the plurality of third-party services;
provide the query and an authentication token associated with a user to the particular connector;
retrieve information associated with the query from the particular connector for the particular third-party service; and
provide the information to the client application executing on the client device.
2. The system of claim 1 , wherein, when executed, the at least one application causes the at least one computing device to at least parse the query into one or more terms.
3. The system of claim 2 , wherein the connector data comprises a list of keywords, and the particular connector is identified in an instance in which the particular connector is mapped to a particular keyword in the list of keywords that matches the one or more terms.
4. The system of claim 1 , wherein the connector data comprises a list of structures, and the particular connector is identified in an instance in which the particular connector is mapped to a particular structure in the list of structures that matches a structure of the query.
5. The system of claim 1 , wherein, when executed, the at least one application causes the at least one computing device to at least determine that the particular connector is enabled by the user.
6. The system of claim 1 , wherein providing the information to the client application executing on the client device comprises sending the information and user interface code to the client application, the user interface code being configured to generate a user interface element including the information from the particular third-party service.
7. The system of claim 1 , wherein providing the information to the client application executing on the client device comprises:
generating a user interface element comprising the information associated with the particular third-party service; and
transmitting the user interface element to the client device.
8. A method for integrating related third-party services for user interaction, the method comprising:
receiving, by at least one computing device and over a network, a query from a client application executing on a client device, the query comprising a selection of content from a user interface of the client application;
identifying, by the at least one computing device, a particular connector associated with the query from a plurality of connectors by comparing the query with connector data, the connector data comprising at least one of a keyword or a structure being mapped to a respective connector of the plurality of connectors, the plurality of connectors being associated with a plurality of third-party services, and the particular connector providing access to a particular third-party service of the plurality of third-party services;
providing, by the at least one computing device, the query and an authentication token associated with a user to the particular connector;
retrieving, by the at least one computing device, information associated with the query from the particular connector for the particular third-party service; and
providing, by the at least one computing device, the information to the client application executing on the client device.
9. The method of claim 8 , further comprising parsing the query into one or more terms.
10. The method of claim 9 , wherein the connector data comprises a list of keywords, and the particular connector is identified in an instance in which the particular connector is mapped to a particular keyword in the list of keywords that matches the one or more terms.
11. The method of claim 8 , wherein the connector data comprises a list of structures, and the particular connector is identified in an instance in which the particular connector being is mapped to a particular structure in the list of structures that matches a structure of the query.
12. The method of claim 8 , further comprising determining that the particular connector is enabled by the user.
13. The method of claim 8 , wherein providing the information to the client application executing on the client device comprises sending the information and user interface code to the client application, the user interface code being configured to generate a user interface element including the information from the particular third-party service.
14. The method of claim 8 , wherein providing the information to the client application executing on the client device comprises:
generating a user interface element comprising the information associated with the particular third-party service; and
transmitting the user interface element to the client device.
15. A non-transitory computer readable medium for integrating related third-party services for user interaction, the non-transitory, computer readable medium comprising machine-readable instructions that, when executed by a processor of at least one computing device, cause the at least one computing device to at least:
receive, over a network, a query from a client application executing on a client device, the query comprising a selection of content from a user interface of the client application;
identify a particular connector associated with the query from a plurality of connectors by comparing the query with connector data, the connector data comprising at least one of a keyword or a structure being mapped to a respective connector of the plurality of connectors, the plurality of connectors being associated with a plurality of third-party services, and the particular connector providing access to a particular third-party service of the plurality of third-party services;
provide the query and an authentication token associated with a user to the particular connector;
retrieve information associated with the query from the particular connector for the particular third-party service; and
provide the information to the client application executing on the client device.
16. The non-transitory computer readable medium of claim 15 , wherein the machine-readable instructions, when executed by the processor of the at least one computing device, further cause the at least computing device to at least parse the query into one or more terms.
17. The non-transitory computer readable medium of claim 16 , wherein the connector data comprises a list of keywords, and the particular connector is identified in an instance in which the particular connector is mapped to a particular keyword in the list of keywords that matches the one or more terms.
18. The non-transitory computer readable medium of claim 15 , wherein the connector data comprises a list of structures, and the particular connector is identified in an instance in which the particular connector is mapped to a particular structure in the list of structures that matches a structure of the query.
19. The non-transitory computer readable medium of claim 15 , wherein the machine-readable instructions, when executed by the processor of the at least one computing device, further cause the at least computing device to at least determine that the particular connector is enabled by the user.
20. The non-transitory computer readable medium of claim 15 , wherein providing the information to the client application executing on the client device comprises sending the information and user interface code to the client application, the user interface code being configured to generate a user interface element including the information from the particular third-party service.