Actions50
- Company Actions
- MS Manual Actions
- Company Information Actions
- Organisation Chart Actions
- Products & Services Actions
- Design & Development Actions
- Scope of Certification Actions
- Key Processes Actions
- Interested Parties Actions
- USPs Actions
- Finalise Policy Actions
- Normative References Actions
- List of Assets Actions
- Risk Assessment Actions
- Objectives Actions
- Customer Feedback Criteria Actions
- Supplier Evaluation Actions
- Supplier Evaluation Criteria Actions
- Terms and Definitions Actions
- Hazard Identification Actions
- Elimination of Hazards Actions
- Multi-employer workplace Actions
- Workers Representative Actions
- Annex A Controls Actions
- Communication Actions
- Finalise Manual Actions
- Finalise SOA Actions
- Status Actions
- Task Actions
- User Actions
- Workflow Actions
- Workflow Entry Actions
Workflow Entry → Create Workflow Entry
AI-generatedSummary
Create a workflow entry for the specified workflow, optionally including a description, step assignments, and metadata. The node sends a POST request and returns the API response as an n8n item.
Inputs
- Base URL Override — Optional base URL for this node; overrides the URL in the required MSFrog credentials.
- Workflow UUID (required) — UUID of the workflow to create an entry for.
- Entry Name (required) — Name for the new workflow entry.
- Description — Optional description; defaults to an empty string.
- Step Assignments — JSON array of step assignment objects using backend field names; defaults to an empty array.
- Meta (JSON) — Optional JSON metadata to store with the entry, such as email or thread IDs; defaults to an empty object. The node can also merge messageId/email_id and threadId/thread_id values from the input item's meta, workflowEntryMeta, or emailMeta fields into email_ids and thread_ids.
Output shape
One n8n item per input item, containing the API response to the create request.
Sends POST /api/userworkflows with workflow_uuid, name, description, and step_assignments; includes meta only when nonempty. JSON fields accept JSON text or parsed values; invalid JSON raises an operation error.