Search for answers or browse articles about Sintel Apps
The Workflow Actions API Integration
The Allow Automated Submission option enables a workflow action to be triggered programmatically via the Sintel Apps API.
When enabled, the action can run without a user manually clicking the action button in the form interface.
This feature is typically used for:
-
System-driven processes
-
Integrations with other Microsoft services
-
Background automation
-
Removing manual intervention steps
What Does “Allow Automated Submission” Do?
When this option is enabled on a workflow action:
-
The action becomes available via a secure API endpoint.
-
The action can be triggered from Power Apps / Power Automate.
-
No user interaction inside the form is required.
-
The workflow status updates exactly as if the button had been clicked manually.
This allows external systems to progress a form through its workflow automatically.
A common example:
A team submits a request form in Sintel Apps.
Once a related SharePoint item is created (e.g., a background check or document verification), you want the form to automatically move to the next approval stage.
Instead of someone opening the form and clicking a button, Power Automate can:
- Detect the SharePoint item creation.
- Call the Sintel Apps API.
- Automatically trigger the workflow action.
- Move the form from “Initial” to the next status.
This removes delays and manual effort.
How to Configure Automated Submission
Step 1 – Enable Allow Automated Submission
- Open the form in Designer.
- Go to the required Workflow Action.
- Scroll to the bottom of the Action Properties panel.
- Enable Allow Automated Submission.
- Copy the API Integration URL shown.
You will use this URL inside Power Automate.
Step 2 – Create a Flow in Power Automate
- Go to Power Automate.
- Create a new Automated Cloud Flow.
- For testing, use the trigger:
When an item is created (SharePoint trigger)
Configure:
-
Site Address
-
List Name (e.g., Automation API Test List)
Step 3 – Add the Correct HTTP Action (Important)
You must use:
Invoke an HTTP request
Category: HTTP with Microsoft Entra ID (pre-authorised)
This is a Premium connector.
Step 4 – Configure the HTTP Action
Method
Must be:
GET or other methods will not work.
URL
- Paste the API URL copied from the form.
- In the URL you will see:
- Remove {formItemId}.
- Replace it with:
-
-
A static Item ID (for testing), OR
-
The dynamic ID from the trigger (recommended)
-
Do not change:
-
Site ID, List ID, Action ID
Authentication Settings: When configuring the HTTP action:
Authentication Type:
Login with Microsoft Entra ID
Use:
-
Base Resource URL (e.g. https://app.sintelapps.com)
-
Application (Client) ID / API ID (provided internally)
Important Notes
-
Demo and Live environments use different API URLs.
-
If testing on Demo, you must use the Demo API ID.
-
The flow runs under the credentials of the signed-in user.
-
A Premium Power Automate licence is required.
Step 5 – Test the Flow
- Create a new item in the SharePoint list.
- Wait approximately 30 seconds.
- Open Flow Run History – it should show Succeeded.
- Refresh the form item.
- The workflow status should change (e.g., from Initial to the next stage).
If the status updates correctly, the HTTP invocation is working.
When Should You Use This?
You might use Allow Automated Submission when:
-
A background screening system confirms clearance → form moves to “Cleared”.
-
A finance system confirms payment has been received → form moves to “Paid”.
-
A compliance platform validates required documents → form moves to “Verified”.
-
A Power App captures inspection results → form moves to “Inspection Complete”.
-
A SharePoint list records that stock has been allocated → form moves to “Ready for Dispatch”.
-
A contract management system marks an agreement as signed → form moves to “Executed”.
-
An HR system confirms a start date → onboarding form moves to “Approved for Provisioning”.