Inter-Platform Control Interface

1. A client-server system defining a first platform comprising: a backend canvas service executing by operation of a processor and a memory allocated to a host server, the backend canvas service configured to: communicably couple to a frontend instance of a second platform separate from the first platform, the frontend instance executing by operation of a client device comprising a display, the frontend instance configured to render a graphical user interface via the display, the backend canvas service providing a rich content editing canvas integrated within the graphical user interface of the frontend instance of the second platform, the backend canvas service providing the same rich content editing canvas integrated within a graphical user interface of another frontend instance of a third platform separate from the first platform and the second platform; receive, from the frontend instance, information comprising: a token identifying an authenticated user of the first platform; and a text input received by the rich content editing canvas; determine that the text input is prefixed with a recognized string; extract a candidate instruction substring from a portion of the text input succeeding the recognized string; select, from a set of executable instructions hosted by the backend canvas service, a subset of executable instructions associated with operations executable by the first platform, wherein each selected executable instruction comprises an attribute string containing the candidate instruction substring; transmit the subset of executable instructions to the frontend instance of the second platform, thereby causing to be rendered, in the rich content editing canvas integrated within the graphical user interface of the frontend instance of the second platform, the subset of executable instructions; and in response to receiving a selection of a particular executable instruction from the subset of executable instructions, cause to be executed, on the first platform, a particular operation associated with the particular executable instruction.

2. The first platform of claim 1, wherein the backend canvas service is configured to: receive from the first platform a result of execution of the particular operation associated with the selected executable instruction by the first platform; and causing to be displayed in the graphical user interface an indication corresponding to the result.

3. The first platform of claim 1, wherein the backend canvas service is configured to filter the subset of executable instructions to remove executable instructions that the authenticated user, identified by the token, is not permitted to cause to be executed on the first platform.

4. The first platform of claim 1, wherein the backend canvas service is configured to normalize the candidate instruction substring prior to selecting the subset of executable instructions.

5. The first platform of claim 4, wherein normalizing the candidate instruction substring comprises one or more of: lemmatizing the candidate instruction substring; tokenizing the candidate instruction substring; or changing a case of the candidate instruction substring.

6. The first platform of claim 1, wherein the recognized string comprises a nonalphanumeric character.

7. The first platform of claim 1, wherein: the token is a first token; the authenticated user is a first authenticated user; and the backend canvas service is configured to obtain a second token identifying a second authenticated user of the second platform.

8. The first platform of claim 7, wherein the backend canvas service is configured to obtain the second token from a single sign-on service communicably coupled to each of the first platform and the second platform.

9. The first platform of claim 7, wherein the backend canvas service is configured to obtain the second token from the second platform.

10. The first platform of claim 7, wherein the backend canvas service is configured to: receive from the frontend instance, information comprising the second token identifying the authenticated user of the second platform; and a selection of an executable instruction from the ordered subset of executable instruction; and causing to be executed, by the second platform, the selected executable instruction.

11. A client-server system defining a first platform comprising: a backend canvas service executing by operation of a processor and a memory allocated to a host server, the backend canvas service configured to: communicably couple to a frontend instance of a second platform separate from the first platform, the frontend instance executing by operation of a client device comprising a display, the frontend instance configured to render a graphical user interface via the display, the backend canvas service providing a rich content editing canvas integrated within the graphical user interface of the frontend instance of the second platform, the backend canvas service providing the same rich content editing canvas integrated within a graphical user interface of a frontend instance of a third platform separate from the first platform and the second platform; receive, from the frontend instance of the second platform, a text input from a user of the client device entered via the rich content editing canvas; receive a token authenticating the user to the first platform from the frontend instance of the second platform; transmit, to the frontend instance, an ordered subset of executable instructions of a set of executable instructions hosted by the backend canvas service, each executable instruction of the subset of executable instructions associated with a respective operation executable by the first platform; and cause to be rendered in the graphical user interface of frontend instance of the second platform, the ordered subset of executable instructions.

12. The first platform of claim 11, wherein the frontend instance of the second platform is configured to render the ordered subset of executable instructions within an overlay window rendered below the rich content editing canvas.

13. The first platform of claim 11, wherein the backend canvas service is configured to parse the text input to determine whether the text input contains a recognized string.

14. The first platform of claim 13, wherein the recognized string comprises a nonalphanumeric character.

15. The first platform of claim 11, wherein the first platform is a documentation platform and the second platform is an issue tracking system platform.

16. A method of triggering actions by a backend of a second platform from a frontend of a first platform, the method comprising: hosting, at the backend of the second platform, a set of executable instructions; receiving at the frontend a first user input comprising a text string; determining that the text string is prefixed with a recognized string; extracting from the text string, after the recognized string, a candidate instruction string; selecting, by the backend of the second platform, the second platform from a list of candidate platforms separate from the first platform based on at least one of the candidate instruction string or the recognized string; filtering, by the backend of the second platform, the set of executable instructions to obtain a list of executable instructions associated with the second platform based on one or executable instructions previously selected by the user; causing to be rendered in a graphical user interface of the frontend of the first platform, the filtered list of executable instructions; receiving at the frontend a second user input comprising a selection of one of the filtered list of executable instructions; and causing to be executed by the second platform, the selected executable instruction.

17. The method of claim 16, wherein determining that the text string is prefixed with the recognized string is performed by the frontend.

18. The method of claim 16, wherein determining that the text string is prefixed with the recognized string is performed by a backend of the first platform.

19. The method of claim 16, further comprising: prior to selecting the second platform from the list of candidate platforms, causing to be rendered in the graphical user interface of the frontend the list of candidate platforms; and receiving at the frontend a third user input comprising a selection of the second platform.