Requesting a custom automation
When nothing in the catalogue fits, this form sends the idea to the Sparkia team rather than leaving you to bend an existing template into the wrong shape.
/automations/requestAnyone signed in and belonging to an organization.
What the form asks
Five sections, filled top to bottom. The more concrete the answers, the less back and forth before anything gets built.
| Section | What it covers |
|---|---|
| Basic Information | A clear title, a category, and a detailed description of what the automation should do. The description needs at least twenty characters, which is deliberate: a one-line request cannot be scoped. |
| Use Case and Requirements | Why you need it and what you expect to get out. Optionally, how you handle this today and what tools would have to connect. |
| Project Details | Priority, timeline and an optional budget band. These set expectations rather than committing anyone. |
| Supporting Documents | Optional. Images, documents, PDFs or JSON, up to 5 MB each. A mockup or an example of the output you want is worth more than a paragraph describing it. |
| What happens next | A summary of the process, and the submit button. |
Writing a request worth building
The two fields that decide whether a request can be acted on are the business use case and the expected output.
| Instead of | Write |
|---|---|
| Automate our social media | We post three times a week to Instagram and it takes a morning. We want a weekly draft set we can approve rather than write. |
| Better content | Three captions with hashtags and one image prompt each, ready to review on Monday morning. |
Describing your current manual process is the single most useful optional field. It says what is actually being automated.
After you submit
The form states the process next to the submit button: the team reviews within a day, gets in touch to discuss whether it is feasible, sends a timeline and quote if it is, and builds it once agreed.
A confirmation appears and you are returned to the workspace. The request itself is not shown back to you anywhere in the app, so keep your own note of what you asked for.
Fields that are too short are flagged inline rather than on submit, so nothing is lost by trying.
Worth knowing
Check the automation catalogue first. A number of requests turn out to be something that already exists under a different name.
Priority and timeline are your assessment of urgency, not a service level. They help order the queue.
The budget band is optional and exists so a proposal can be pitched at the right size. Leaving it blank does not disadvantage the request.