> For the complete documentation index, see [llms.txt](https://docs.wem.io/platform/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wem.io/platform/tutorials/video-tutorials/by-partners.md). # By Partners Video tutorials provided by WEM Partners ## PIM-21: [pim-21.com](https://pim-21.com/) At PIM we are hooked on WEM No-Code. WEM is a no-code application development platform. It allows for developing applications 10x faster. And you hardly need any IT technical knowledge. But don't get this wrong, WEM allows for developing full-fledged business applications. We have developed bookkeeping applications, community software, and building maintenance software. Even governments have selected WEM as a platform for developing their mission critical applications! [This channel](https://www.youtube.com/@pimonwemno-code1725) is devoted to WEM No-Code. You'll find a wide range of tutorial video's and testimonials. Enjoy! {% embed url="" %} WEM No Code Tutorial 1: Introduction {% endembed %} {% embed url="" %} WEM No Code Tutorial 2: Sending an email {% endembed %} {% embed url="" %} WEM No Code Tutorial 3: Import and export {% endembed %} {% embed url="" %} WEM No Code Tutorial 4: Accessing a SOAP webservice {% endembed %} {% embed url="" %} WEM No Code Tutorial 5: Accessing a REST webservice {% endembed %} --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.wem.io/platform/tutorials/video-tutorials/by-partners.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.