<img height="1" width="1" style="display:none;" alt="" src="https://ct.pinterest.com/v3/?event=init&amp;tid=2612519005006&amp;noscript=1">
Skip to content
English
  • There are no suggestions because the search field is empty.

Build your first connector workflow: Marq Approvals

Automate your brand approval process by connecting Marq to Project Management tools like Monday.com, Asana and Wrike to create a sophisticated workflow management without compromising brand oversight or creative team efficiency.

What you'll build

A workflow that listens for approval requests in Marq and automatically creates a corresponding task or item in your team's project management tool. Whenever someone in your account submits a design for approval, a card lands on your review board with the project title, requester info, a link back to the Marq project, and any reviewer comments.

This guide walks through the workflow editor concepts that apply to every connector. For connector-specific setup (authentication, board/folder selection, and field mapping), follow the links in Steps 5–7.


Before you start

You'll need:

  • An admin account in Marqet
  • An account in your target connector app with permission to create items
  • Your connector app set up and ready to receive items (see your connector's setup guide below)

Step 1 — Create a new workflow

  1. In the Marqet admin panel, navigate to My Apps → New.
  2. Click Workflow.
  3. Give it a name (e.g., "Approvals → Monday Review Board") and click Create.

You'll land in the visual workflow editor — a blank canvas with a single empty trigger node.


Step 2 — Configure the Marq Approvals trigger

  1. Click the trigger node on the canvas.
  2. In the right-hand config panel, search for Marq and select it as your trigger app.
  3. Choose the event type: Approval Requested (approval.pending).
  4. Click Activate Listener.

What "Activate Listener" does: Marqet registers a webhook with the Marq API on your account's behalf. From this moment forward, any approval request created in Marq will be delivered to your workflow in real time.

You'll see the listener status flip from Inactive to Active, and the trigger node on the canvas will show a green indicator.


Step 3 — Run a test approval

Before connecting any downstream actions, confirm the listener is actually receiving Marq events. You have two options:

Option A — Test with a sample payload (fastest)

Click Test with sample data. Marqet uses a built-in sample approval event so you can see exactly what data your workflow will receive.

Option B — Test with a real recent approval (most accurate)

  1. In a separate tab, open Marq and submit any document for approval.
  2. Return to the workflow editor and click Pull recent event.
  3. Select the approval you just created from the list.

Either way, you'll see the full event payload in the trigger's output panel. Expect fields like:

Field Example value
project.title Q1 Marketing Campaign
project.editorUri https://app.marq.com/documents/edit/...
requesterDetails.name Sarah Designer
approvalState pending_approval
comments reviewer notes

If you see this data, the listener is working.


Step 4 — Add a connector action

  1. Click the + button below the trigger node.
  2. Search for your connector app and select Create Item (Monday.com) or Create Task (Wrike, Asana) as the action.

The action node appears, connected to your trigger.


Step 5 — Connect your app

Authenticate Marqet with your connector. Each app handles this slightly differently:

  • Connect Monday.com to Marqet
  • Connect Wrike to Marqet
  • Connect Asana to Marqet

Once connected, return here and continue with Step 6.


Step 6 — Select your destination

After authenticating, choose where new items should land in your connector app:

  • Monday.com — select a Board from the dropdown. Marqet loads your available boards and then that board's columns automatically.
  • Wrike — select a Folder (and optionally a Parent Project). Marqet loads your folder list from Wrike.
  • Asana — select a Workspace, then a Project. Switching workspaces resets the project selection.

Step 7 — Map Marq fields to your connector

This is where the workflow becomes useful. You're telling Marqet which piece of approval data goes into which field in your connector app.

Use template variable syntax to pull data from the trigger: @{trigger-1.field.path}. For example:

Variable What it contains
@{trigger-1.project.title} The project name
@{trigger-1.requesterDetails.displayName} Who submitted the approval
@{trigger-1.project.editorUri} Direct link to the Marq project
@{trigger-1.comments} Reviewer comments

You can mix variables with literal text: Approval needed: @{trigger-1.project.title}

For field-by-field mapping guidance specific to your connector, see the setup articles linked in Step 5.


Step 8 — Run a test

Click Test Run in the top-right of the editor.

Marqet replays your sample (or selected real) approval event through the workflow, end to end. Each node lights up as it executes:

  • 🟢 Green border = success
  • 🟡 Yellow = running
  • 🔴 Red = failed (click for error details)

If the test succeeds, switch to your connector app and confirm the test item was created.


Step 9 — Publish the workflow

When you're satisfied, click Publish in the top-right.

Publishing:

  • Promotes your draft configuration to live
  • Begins routing real approval events through the workflow
  • Enables the workflow's Active toggle

From this moment, every approval request in your Marq account will create a corresponding item in your connector app.


Step 10 — Monitor executions

Navigate to Admin → Workflows → [your workflow] → Runs to see every time the workflow has fired.

For each run you'll see:

  • Status (completed, failed, processing)
  • Timestamp and duration
  • The exact trigger payload Marq sent
  • Whether the downstream item was created successfully
  • Any error messages

For full details, see Monitor and manage your workflows.


Troubleshooting

Symptom Likely cause
Test approval doesn't appear in trigger Listener not activated, or token expired — re-activate from the trigger panel
Item created but missing fields Field type mismatch — verify your mappings match the column/field types in your connector app
Test run fails on action node Permissions changed in your connector app — reconnect or pick a different destination
Real runs aren't firing Workflow is in draft — confirm you clicked Publish, not just Save