Resources · Make integration

Dribbble Make integrationAutomate Dribbble with Make.

Can Make publish and tidy your Dribbble portfolio for you? Yes. The Dribbble Make integration gives you 12 modules: 2 scheduled triggers, 8 actions and 2 searches over shots and projects. This guide takes designers and studio leads from the connection to a first working scenario.

Try the Dribbble integration on MakeSee the 12 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dribbble Make integration automate?

The Dribbble Make integration links your Dribbble account to Make, so a scenario (the automation you build in Make, a chain of modules) can notice new shots and projects, create or update them, and pull the full list of your work. No code is involved: you pick modules in the Make editor and connect the Dribbble account you already use.

Every new shot echoed where your team looks. Watch Shots notices each shot you post, and the next module sends it wherever the team follows the work: a chat channel, a spreadsheet, a newsletter draft. Dribbble stays the one place where you publish.

Projects opened from your client pipeline. When a deal is signed in another tool, Create a Project opens the matching project on Dribbble, and Update a Project keeps it in step as the brief evolves.

A clean inventory of your work. List Shots and List Projects return everything the account holds, which is handy for a report or to feed Get a Shot, Update a Shot or Remove a Shot.

What Make does not do here: Dribbble has no instant trigger, so new shots and projects are picked up on the scenario's schedule, not the moment they appear. Anything outside the listed modules goes through Make an API Call. The same app often has an n8n node too; the n8n vs Make comparison lays out the criteria, and Make pricing explains how usage is counted. Prefer a guided start? See Make training.

Connect

How do you connect Dribbble to Make?

  1. 01

    Register an application on Dribbble

    Dribbble signs Make in through OAuth, so Make needs its own application on your account. In your Dribbble account settings, open Applications (or Developer Applications), click New Application, fill in the required fields and paste the callback URI https://www.integromat.com/oauth/cb/dribbble.

  2. 02

    Copy the two credentials

    Click Create Application. Dribbble then displays a Client ID and a Client secret. Copy both and keep them at hand: Make asks for them in the next step, and they are what allows it to act on your shots and projects.

  3. 03

    Create the connection in Make

    Add any Dribbble module to a scenario and click Create a connection. Type a Connection name if you like, then paste the credentials or follow the on-screen instructions. A connection is your Dribbble account linked to Make once, and every Dribbble module reuses it.

First scenario

Your first scenario: open a Dribbble project from a signed deal

GoalWhen a new deal or brief lands in another app, Make creates the matching project on Dribbble.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big +. The first module you choose is the trigger: the brick that decides when the scenario starts.

  2. 02

    Pick the app where deals live

    Search the tool that holds your deals or briefs and choose its trigger module. Link that account with Create a connection, then fill the fields: Make lists what it can read once the connection exists.

  3. 03

    Add Create a Project

    Click the + on the right of the first module, search Dribbble and pick Create a Project. Select your Dribbble connection and map the data coming from the first module into the project.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received (a bundle is one item passed from a module to the next). Then check on Dribbble that the project looks right.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default, which is also the floor on the Free plan. Adjust the schedule if your plan allows it, then switch the scenario on.

Triggers

Which Dribbble triggers can start a scenario?

2 modules start a scenario when something happens in Dribbble. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Dribbble as soon as it happens.

Dribbble1Watch Projects

Watch Projects

Scheduled trigger

In Make“Triggers when a new project was created.”

Opening a new project on Dribbble can now set off work in your other tools: Watch Projects spots each project created on your account and hands it to the rest of the scenario.

How it fires
scheduled. Make checks Dribbble on the scenario's schedule, set under Scheduling on the first module, and collects the projects created since the previous check.
When to use it
a studio lead wants each new project to open a task board, a client folder or a note in the team workspace.
Watch out
only new projects count. Editing an existing project does not start the scenario, so changes need another route, such as List Projects in a separate scenario.
Dribbble2Watch Shots

Watch Shots

Scheduled trigger

In Make“Triggers when a new shot was created.”

Every shot you publish becomes the starting point of a scenario: Watch Shots passes each new one to the next module as a bundle, ready to be shared, logged or archived somewhere else.

How it fires
scheduled. Make checks Dribbble on the scenario's schedule, every 15 minutes by default, and the clock badge on the module reminds you of it.
When to use it
your team wants a message or a spreadsheet row whenever a designer posts new work, without anyone copying links by hand.
Watch out
each shot returned costs an operation, meaning one execution of a module that Make counts on your plan, and a shot posted just after a check waits for the next one.
Modules

What can Make do in Dribbble?

Dribbble gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Dribbble1

Create a Project

Action

In Make“Creates a project.”

A fresh project on Dribbble, opened by the scenario instead of by hand: Create a Project adds one to your account from the data the previous module delivers.

When to use it
a deal marked as won in your CRM should give the design team its project on Dribbble straight away.
Watch out
every run adds another project, so a record processed twice leaves you with two. Try it with Run once on a test record first.
Dribbble2

Create a Shot

Action

In Make“Creates a shot.”

Publishing work from a scenario is what this module covers: Create a Shot posts a new shot to your Dribbble account with the content the earlier modules prepared.

When to use it
a visual approved in your review tool, or dropped into a shared folder, is ready to go on Dribbble.
Watch out
the shot goes out under your name, so keep a human check before this module rather than posting everything that reaches it.
Dribbble3

Get a Shot

Action

In Make“Gets the authenticated user's shot by ID.”

Holding only a shot's ID is enough here: Get a Shot fetches that single shot from your account with its details, so the following modules can reuse them.

When to use it
another module or app hands you the ID, and you need the rest of the shot before writing a report or a message.
Watch out
the module is meant for shots of the connected account, so pass an ID that comes from your own portfolio.
Dribbble4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Anything the other modules leave out stays within reach: Make an API Call sends a request to any endpoint of the Dribbble API, using the connection you already set up.

When to use it
you need a Dribbble feature that no listed module offers, and you are comfortable reading the API documentation.
Watch out
you write the request yourself, so test it with Run once and read the returned bundle before building anything on top.
Dribbble5

Remove a Project

Action

In Make“Removes user's project by ID.”

Clearing out a project that no longer belongs in your portfolio takes one module: Remove a Project deletes it by its ID.

When to use it
a client contract ends and the related project should leave Dribbble as soon as the deal is closed in your CRM.
Watch out
a deletion cannot be undone from Make, so get the right ID first with List Projects and rehearse on a test project.
Dribbble6

Remove a Shot

Action

In Make“Deletes shot with a specified ID.”

Taking a shot down is the job of Remove a Shot, which deletes the one whose ID you provide and cleans your profile without a visit to Dribbble.

When to use it
the client withdrew a visual, or a better version replaced it, and the old one should go.
Watch out
nothing brings the shot back afterwards. Find its ID with List Shots and keep a copy of the files before running it.
Dribbble7

Update a Project

Action

In Make“Updates project by ID.”

Keeping a project in line with reality gets easier with Update a Project, which changes an existing project identified by its ID.

When to use it
the scope of a client job shifts in your project tool, and the Dribbble project should show the new version.
Watch out
the module works from the ID, so place List Projects before it whenever that ID is not already flowing through the scenario.
Dribbble8

Update a Shot

Action

In Make“Updates shot with a specified ID.”

Fixing a shot after it went live no longer means opening Dribbble: Update a Shot edits the shot whose ID you pass to it.

When to use it
a copywriter corrects a published piece in your content calendar, and the change should reach Dribbble too.
Watch out
when the ID comes from List Shots, every shot returned gets the same edit, so test on a single bundle with Run once first.
Dribbble9

List Projects

Search

In Make“Lists all projects for this account.”

A full picture of your projects comes from List Projects, which returns every project of the connected account, each one as a separate bundle.

When to use it
you want an inventory in a spreadsheet, or you need the ID of the project to update or remove.
Watch out
as a search, it can return zero, one or many bundles, and each module after it runs once per project, which multiplies operations.
Dribbble10

List Shots

Search

In Make“Lists the authenticated user’s shots.”

Your whole body of work, one bundle per shot: List Shots returns the shots of the authenticated user so the scenario can go through them one by one.

When to use it
you are building a showcase page or a backup sheet of everything you published on Dribbble.
Watch out
an empty result is a normal answer, not an error, so decide what the next module should do when nothing comes back.
Need help

Need help automating Dribbble with Make?

A person reads every message.

FAQ

Dribbble and Make: common questions

01Is the Dribbble Make integration free?
Yes. Dribbble is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, lift the cap on active scenarios and extend execution to 40 minutes, with usage counted in credits per month. On the Dribbble side, you need an active account; the Dribbble pricing page covers its subscriptions.
02What do you need to connect Dribbble to Make?
An active Dribbble account and an application registered on it. Dribbble relies on OAuth, so you create a new application from the account settings, under Applications or Developer Applications, enter the callback URI provided by Make and copy the Client ID and Client secret shown on screen. In Make, you add a Dribbble module, click Create a connection, name it if you wish, and paste those credentials or follow the on-screen instructions. Every Dribbble module then reuses that connection, so the setup happens only once per account.
03Do the Dribbble triggers in Make fire in real time?
No. Watch Shots and Watch Projects are both scheduled triggers: Make polls Dribbble on the scenario's schedule and collects what was created since the previous check. A new scenario runs every 15 minutes by default, which is also the minimum on the Free plan, while paid plans can go down to 1 minute. Dribbble has no instant trigger in Make, so no webhook warns Make the moment a shot or a project appears. If timing matters to you, shorten the schedule within what your plan allows.
04What if a Dribbble module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the Dribbble API with the connection you already created, so a feature absent from the 12 listed modules can still be reached inside the same scenario. You write the request from the Dribbble API documentation, test it with Run once and read the returned bundle before adding more modules. Also note that the Make documentation for this app is AI-generated from the Dribbble documentation and may contain mistakes, so confirm important details with Dribbble directly.
05Should you use Make or n8n for Dribbble?
It depends on the tool your team already works in. Make offers 12 Dribbble modules, including 2 scheduled triggers, in an editor where each scenario can be tested with Run once before it goes live. The same app often has an n8n node as well, so list the modules your use case needs and check which side covers them. There is no ranking to hand out: pick the tool where the modules you need exist and where the person who maintains the scenarios feels at home.
Same platform

Other docs you might need on this stack.

Browse all integrations