Short answer: Drop the "Suno → Suno Generate Music" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Lyrics / Prompt prompt | string | Required | Lyrics / Prompt (required) |
Style Tags tags | string | Optional | e.g. pop, female vocals, upbeat |
Instrumental Only make_instrumental | options | Optional | Instrumental Only. Options: No, Yes |
Model model | options | Optional | Model. Options: Chirp v4, Chirp v3.5 |
{"prompt": "{{trigger.prompt}}","tags": "e.g. pop, female vocals, upbeat","make_instrumental": "{{trigger.make_instrumental}}","model": "{{trigger.model}}"}
{"code": 0,"data": [{"status": "submitted","song_id": "song-abc"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.