This repository contains the officially maintained connectors for Appmixer. They enable seamless integration with external services and help you build workflows faster by handling API access, authentication, and data flows.
- Ease of use: Pre-built connectors remove boilerplate for common integrations.
- Flexibility: Customize and extend connectors to suit specific needs.
- Scalability: Build workflows that scale with your workloads.
To learn how to create custom connectors, refer to our comprehensive guide: Creating Custom Connectors.
We welcome contributions from the community! To contribute:
- Fork the repository.
- Create a new branch for your feature or bug fix.
- Ensure your code adheres to our coding standards and includes tests.
- Submit a pull request with a clear description of your changes.
Examples can be found in the src/examples directory. They are not exhaustive, but they should give you an idea of how to use the connectors. Examples do not belong to our connector Marketplace, but they are useful for testing and development purposes.
In the test directory, you can find the test files for the connectors. They are not exhaustive as there is another set of tests that are not public.
npm run test-unitIn test/utils.js you can find a stub for the Appmixer API. It is supposed to emulate all the advanced features of the Appmixer engine like sending messages, doing HTTP requests, using cache, etc. It is not a complete implementation of the Appmixer API, but it is enough to test the connectors. You can use it to test your connectors without having to run the Appmixer engine.
These tests run on every PR. They also feed into SonarQube analysis, which runs on each commit to the dev branch.
Rule of thumb:
- A
receivefunction in a component should be tested if it has any logic in it (caching, timeouts, bulk processing). If it is just a pass-through, it does not need to be tested. - A
routes.jsfile should be tested if used for more complex tasks, such as processing incoming webhooks.