The Shuffle ecosystem is built on open source code, and since the start, we've focused on openness and building as good a service as we can. We do however know that we don't know everything, and need help from the community to create as good of a service for our customers as possible. That's why we've launched the creator program - a way we can share revenue with everyone who spend time helping Shuffle grow by creating content like Apps, Workflows and Documentation, along with Blogposts, videos and who do support and github contributions.
You can see our interactive Creator FAQ on the creator pages.
There are no specific prerequisites to become a Creator, but we encourage you to at least know how to build Workflows.
The first thing necessary to become a creator is to sign up to the Shuffle platform. These are the requirements:
With these in place, you can go to the Creator pages and sign up! It only takes a minute. In order to get verified, you will further have to provide your First Name and Last name, along with other optional information.
What and how you can change, what people are interested in, what you can earn from, how it's calculated, where dashboards are.... TBD
To earn with Shuffle, you need to get verified. This is a manual process, as we need certain information in order to transfer money to you.
If you feel ready to get verified, send us an email at email@example.com. This process will be fully automated in the future.
As a verified Creator, you get access to more information. We share with you the following:
You can build and share anything that may be relevant to other users. The focus is on Workflows and Apps, but the following are also a part of earning with Shuffle:
Our goal with Shuffle as a platform is to help you earn and get reach for your workflows and apps, along with other content, such as Blogs, Articles, and Videos. The normal starting point is with building Workflows and Apps, then releasing them.
It's important that content shared through Shuffle has sufficient information, as to help other users find what they're looking for. The search engine is always the starting point, and it's up to you to discoverable.
After releasing a workflow, this happens:
When inside a Workflow you own, and which is public, you will see the buttons for jumping to the Workflow Editor in the bottom left of your screen. By clicking "Edit Workflow", you will have full access to modifying the Workflow the work the best for other users. You can also test it. Make sure it doesn't contain any sensitive information.
By clicking the "Edit" button on the bottom bar, you can make further changes to the workflow. This is the most important information, and is where you should make sure to fill out all significant fields. This also means to link to related documentation, blogposts and other info.
Additionally, if the workflow's type is "Subflow", make sure to add relevant return values in case of failure to the "Default return value" field.
Trigger workflows are workflows that act as "Triggers" for a specific App. The goal with trigger workflows is to get specific information from an App, then hand it over to a Subflow. Subflows are Workflows that receive some "Standard" information, using our Standardized Data scripts. Trigger and Subflows exist to help all users build and experience workflows faster, by acting as templates that Shuffle itself as a platform can stitch together.
A good example of this is Email. A typical usecase is "When I get an email, enrich it and send it to a ticketing system". This is then split into two main sections, and a last section for enrichment:
Here's how the baseline looks before you can modify it:
After it's been modified, it will automatically grab relevant apps from the App Framework. More about that here.
Trigger workflows start something for an app. A good example is to get new emails and sending them to a subflow ("When I get an email"). They are defined by a few key pieces:
Subflows are workflows that receive some data from a Trigger workflow. They use Standardized Data scripts to get data in the same format every time. They are defined by: