Dribbble
Social MediaConnect AI agents to Dribbble, the designer portfolio and community platform. Agents publish and schedule shots, organize them into projects, attach assets, and look up a job listing by id.
What This Integration Enables
Dribbble does not belong in the same mental slot as the schedulers around it, and building a flow that treats it as one will produce something that does not work. Dribbble is a portfolio, and its v2 API is scoped entirely to the authenticated account. List Shots returns your own shots, not a public timeline. Get Shot returns a shot you own. There is no discovery endpoint, no search, and no way to read another designer's work, because the broad read endpoints that existed in the deprecated v1 API are gone. What remains is a small, honest surface for one thing: keeping a studio's or a designer's own portfolio current without a person remembering to do it. Create Shot uploads from a public image URL, Update Shot revises the metadata around it, Create Project and Update Project group shots into collections, and Create Attachment adds supplementary files such as process images, PDFs, or archives to a shot.
Two constraints will shape any flow built here, and neither is negotiable. First, Dribbble is strict about the image: Create Shot requires exactly 400x300 or 800x600, no larger than 8 MB, and GIF, JPG, or PNG, with up to 12 tags. Second, Update Shot cannot replace the image. It changes the title, description, tags, low-profile flag, team attribution, and scheduled publication time, and the picture stays whatever it was. That means a wrong crop is not an edit, it is a Delete Shot followed by a fresh Create Shot, and the replacement is a new shot with a new URL and none of the views the original accumulated. Both uploads also return 202 Accepted while Dribbble processes them asynchronously, so a flow that assumes a synchronous result will report success before there is one. Dribbble publishes no event subscription, so this connector ships no triggers, and access tokens do not expire and issue no refresh token. On the jobs side, be precise: Get Job retrieves one job listing by its numeric id. There is no browse, list, or search over jobs, and creating or updating jobs needs a partner token Dribbble grants only to approved job-board partners, so those writes are not exposed here at all.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The portfolio that keeps up with the work
A studio's projects live in a tracker. When a project moves to shippable, a flow reads the approved presentation crop from Figma and validates it against Dribbble's dimension, size, and format rules before anything is sent. It calls Get Current User to confirm the connected account is eligible to upload, calls List Projects to find the client's portfolio collection or Create Project if this is the first piece for them, and assembles the title, description, and up to twelve tags from the project record. Then it hands the whole package to the designer for approval. The tedious half, which is the crop validation, the project lookup, and the tag assembly, is done. The half that carries someone's name is not.
A shot that ships with its process attached
A shot on its own is a picture. A shot with the process behind it is a portfolio piece. After a shot is created, a follow-up flow calls Create Attachment for each supporting file in the project folder, pulling them by URL: the wireframe sequence, the type specimen, the annotated spec sheet. Each must be under 10 MB and Dribbble processes them asynchronously. The flow records the attachment ids against the project so a later cleanup knows what it added. The designer publishes the finished piece; the flow does the file-by-file uploading that is the reason process work usually never gets attached at all.
Portfolio hygiene ahead of a pitch
Before a new business pitch, the studio wants its Dribbble presence to reflect current capability rather than five years of accumulation. A flow calls List Shots with pagination and List Projects, and cross-references each shot against the studio's own project register in Notion to build three lists: shots for work the studio still does, shots for work it no longer sells, and shots not matched to any registered project. Nothing is deleted. The lists go to the studio lead as a review document, because Delete Shot is permanent and a shot that looks stale to a filter may be the single most-viewed piece the studio has.
Human-in-Loop Highlight
Everything else in this category publishes on behalf of a company. Dribbble publishes on behalf of a person. A shot carries a designer's name, sits on the surface that recruiters and prospective clients read as their professional record, and the connector's own metadata makes the stakes literal: Get Current User returns a can_upload_shot flag, and Update Shot carries a team attribution field that decides who gets credit for the work. Eligibility is not permission. So the agent does every mechanical step it can, then stops in front of Create Shot and asks the designer directly, through the studio's Slack channel: "Ready to publish 'Northwind dashboard' to your Dribbble as an 800x600 shot in the Northwind project, with these 9 tags and team attribution set to the studio. Update Shot cannot replace the image later, so a wrong crop means deleting this shot and losing its URL and view count. Publish?" The agent will not put work under somebody's byline on a rule. It prepares the shot and lets its author say yes, which is what a human-in-the-loop gate is for when the irreversible thing is a reputation rather than a spend.
Agent Capabilities
13 actionsAccount
1- Get Current User Retrieves the authenticated user's profile, including id, name, login, bio, location, avatar, follower count, and the account flags `pro` and `can_upload_shot`. Run it first in any publishing flow, because an account without upload eligibility will fail at Create Shot rather than at connection time.
Shots
5- List Shots Lists the authenticated user's shots, most recent first, with pagination through page and perPage. Note that the v2 API exposes only the connected account's own shots and not the public timeline, so this is an inventory action rather than a research one.
- Get Shot Retrieves a single shot owned by the connected account, including its title, description, dimensions, image URLs, tags, and attachments. Used to resolve a shot id into something a reviewer can judge before any change is proposed against it.
- Create Shot Uploads a new shot from a publicly reachable image URL. Requires the `upload` scope and an eligible account. Dribbble requires the image to be exactly 400x300 or 800x600, no larger than 8 MB, and GIF, JPG, or PNG, with up to 12 tags. Returns 202 Accepted while the upload is processed asynchronously, so confirmation is a follow-up read rather than a return value.
- Update Shot Updates a shot's metadata: title, description, tags, low-profile flag, team attribution, and scheduled publication time. Only the fields you supply change. The shot image itself cannot be replaced through this action, which is the single most important thing to know before publishing anything here.
- Delete Shot Permanently deletes a shot owned by the connected account. Cannot be undone, and the shot's URL, views, and engagement history go with it, so a re-upload is a new piece rather than a corrected one.
Projects
4- List Projects Lists the connected account's projects, which are the collections used to group shots, most recent first with pagination. Used to find the right home for a new shot before it is created.
- Create Project Creates a new project for the connected account. Used at the start of a client engagement so the first shot published for that client has somewhere structured to land.
- Update Project Updates a project's name and description. Only the fields you supply change. Used to keep collection naming aligned with how the studio actually describes its work today.
- Delete Project Permanently deletes a project. The shots inside it are not deleted, so this removes the grouping rather than the work. Cannot be undone.
Attachments
2- Create Attachment Adds a supplementary file to a shot, such as an image, PDF, or archive, pulled from a URL and no larger than 10 MB. Dribbble processes attachments asynchronously and returns 202 Accepted. This is how process work reaches a portfolio piece instead of staying in the project folder.
- Delete Attachment Permanently deletes an attachment from a shot. Cannot be undone, so cleanup flows should propose rather than execute.
Jobs
1- Get Job Retrieves a single Dribbble job listing by its numeric id, including the organization, title, location, and application link. This is a lookup by known id, not a browse or a search, and there is no action here that lists or discovers jobs. Creating and updating jobs requires a partner token Dribbble grants only to approved job-board partners, so those operations are not exposed by this connector.
Frequently Asked Questions
What can FlowRunner do with Dribbble?
FlowRunner agents can run Get Current User, List Shots, and Get Shot in Dribbble, plus 10 more actions.
Does connecting Dribbble to FlowRunner require OAuth?
Yes. Dribbble connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can Dribbble trigger a FlowRunner workflow automatically?
Dribbble doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Dribbble
$100 in credits. No card required. Connect in minutes.