Delesign
Project ManagementConnect AI agents to Delesign, a subscription graphic design service with a managed request queue. Agents submit design briefs as projects, send messages to designers, and retrieve finished files.
What This Integration Enables
Delesign sells design as a subscription with a queue. You submit briefs, staff designers work through them, and your throughput is governed by how many requests you have in flight rather than by how many hours you buy. That model is the reason this connector matters and also the reason it needs a gate. Every Create Project call consumes a real slot in a real queue against a paid subscription, and there is no draft state: a project created through the API starts in the In Queue status immediately.
What FlowRunner adds is the part around the queue. Agents raise a request the moment the work that needs it is approved somewhere else, so the brief reaches the designer with the audience, timeframe, inspiration and required output formats that were already written down in the plan instead of being summarized into a sentence. They watch status on a schedule and route a completed design to the reviewer. They save delivered assets into FlowRunner file storage so the file can be attached to a card, uploaded to a CMS or dropped into a drive without anyone downloading it first. And they post feedback into a project thread when a reviewer signs off elsewhere.
Two honest boundaries. This connector has no triggers. Delesign publishes no webhook subscription API and no callback payload shape, so there is nothing for FlowRunner to subscribe to. Reacting to design activity means polling List Projects filtered by status, or Get All Projects, on a schedule and comparing the modified timestamp or status between runs. Projects come back most recently updated first, so a single first page is usually enough to detect change, which keeps the poll cheap. The second boundary is one-way visibility: Send Project Message is write-only. The API exposes no endpoint for reading a project's message thread. An agent can post feedback into a conversation it can never read back, which means it cannot see the designer's reply, cannot confirm its own message landed with the right wording, and cannot detect that it has now said the same thing twice. Treat the thread as an outbox, and keep a person on the content of anything the agent writes there.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The content calendar raises its own design requests
A marketing team runs its plan in Airtable. When a row moves to Needs Design, a flow reads the brief fields that the strategist already filled in, checks the category rules locally, and assembles the request. It calls Search Projects first with the campaign name to make sure the same brief has not already been submitted under a slightly different title, since a duplicate costs a queue slot rather than just being untidy. The design owner approves, Create Project submits it, and the returned project ID goes back onto the Airtable row so the plan and the queue point at each other. The brief that reaches the designer is the one the strategist wrote, not a paraphrase of it.
Delivered designs land where the reviewer already works
A scheduled flow calls List Projects filtered to Completed and compares against the last run. For each newly completed project it calls Get Project Details, which adds the delivered designs, the assigned designer and the brand and credential attachments that the list view leaves out. It then calls Save Design File To FlowRunner on each delivered asset URL, which pulls the file from Delesign's own storage into FlowRunner file storage and hands back a URL later steps can use. From there the asset attaches to the campaign card in Trello and the reviewer gets a message with the design in front of them. Nobody downloads anything.
A throughput report built from the account record rather than from memory
Get Account Details returns project counts broken down across the queued, active and completed states, for both company projects and your own, alongside the active subscriptions and their assigned designers. A weekly flow reads that record, walks the in-flight work with Search Projects or Get All Projects, and writes a row into Google Sheets: how many requests are queued, how many are moving, which have been active longest, and who is assigned. A subscription design service is bought on throughput, and this is the report that tells you whether you are actually getting it. Bound the walk with Maximum Projects Scanned on a large account, because Delesign publishes no server side search and Search Projects pages the list and filters inside FlowRunner, costing one request per page scanned.
Human-in-Loop Highlight
Create Project is not a record write, it is a purchase. The moment the call succeeds, a real brief is sitting in a real designer's queue on a paid subscription, in the In Queue status, with no draft state to hold it and no cancel action in the API. The only way to remove it is Delete Project, which Delesign documents as permanently deleting the project together with all of its messages and files, with no restore endpoint and no way to list deleted projects. So the recovery from a bad submission is either to burn the slot or to destroy the record of it. Making this worse, the agent cannot talk its way out afterwards, because Send Project Message is write-only and it will never see the designer's reply. So the agent assembles and stops. It builds the brief from the plan, validates the conditional requirements that Delesign enforces with an unhelpful blanket 422, runs Search Projects to check for a near-duplicate, and asks the design owner: "Ready to submit 'Q3 launch hero, App Design Mockup' to the queue. Mockup type Mobile, screen Onboarding, formats PNG and Figma. Nearest existing request is 'Q3 launch banner' from 4 August, still Active. Submitting takes a queue slot and cannot be cancelled, only deleted. Send it?" A person reads the brief that a designer is about to read, and answers. The agent then calls Create Project, and writes the ID back where the team can find it.
Agent Capabilities
11 actionsAccount
2- Verify API Token Checks that the configured Delesign token is valid by calling the authorize endpoint, returning the message "Authorized." when accepted. Use it as a cheap connection check at the start of a flow, or after rotating the token, so later steps do not fail on an expired credential.
- Get Account Details Retrieves the account tied to the configured token: account holder name and email, roles, account status, company profile fields, active subscriptions with their assigned designers, invited team members, and project counts broken down by company and own projects across the queued, active and completed states. This is the throughput report in a single call.
Projects
7- List Projects Returns one page of design projects, most recently updated first. Filter by author scope, company wide or your own, and by project status. The response carries a has_more flag, so pair it with the Page parameter to walk a large account. With no triggers available, this is the polling surface for design activity.
- Get All Projects Walks every page of the project list and returns the combined array so a flow does not loop itself. Stops at the requested maximum or a safety cap of 50 pages, and reports truncated: true when the cap is hit. Bound it with Maximum Projects on a large account.
- Search Projects Finds projects whose title, description or category contains the given text. Delesign publishes no server side search, so this pages the list and filters inside FlowRunner, costing one request per page scanned. Narrow it with the Status and Author filters and Maximum Projects Scanned.
- Get Project Details Retrieves the full record for a single project. Compared with the list response this adds the brief fields, target audience, timeframe and inspiration, the requested output file types, the assigned designer and their schedule, followers, attached brands and credentials, and the delivered designs.
- Create Project Submits a new design request to the Delesign queue. Title, description and project type are always required, and a category is required when the type is Designs. Video categories additionally require a script; the two mockup categories require a mockup type and the screen being mocked up. Attachments are publicly reachable file URLs, not uploaded bytes. The created project starts In Queue immediately, with no draft state.
- Update Project Updates an existing project with the values supplied. Parameters left empty are not sent and the corresponding values are left unchanged. Delesign marks title, category and description as required on this endpoint, so supply them even when they are not changing.
- Delete Project Permanently deletes a project together with all of its messages and files. Delesign documents this as irreversible: there is no restore endpoint and no way to list deleted projects. Returns "Success." when the deletion is accepted.
Messages and Files
2- Send Project Message Posts a message to a project's conversation thread on behalf of the account that owns the token. Use it for feedback on a delivered design, an answer to a designer's question, or context added to a brief after submission. An optional attachment is passed as a publicly reachable file URL. The API offers no endpoint for reading the thread back, so this is a one way channel.
- Save Design File To FlowRunner Downloads a Delesign asset from its URL into FlowRunner file storage and returns a URL that later steps can use. Take the source URL from a project record, such as the cover image, an attachment, or a delivered design. Delesign serves these assets from its own storage rather than through the API, so this action fetches the URL directly and deliberately does not send your token to the asset host.
Frequently Asked Questions
What can FlowRunner do with Delesign?
FlowRunner agents can run Verify API Token, Get Account Details, and List Projects in Delesign, plus 8 more actions.
Does connecting Delesign to FlowRunner require OAuth?
No. Delesign connects to FlowRunner with an API key, no OAuth flow required.
Can Delesign trigger a FlowRunner workflow automatically?
Delesign doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Delesign
$100 in credits. No card required. Connect in minutes.