FORMLOVA
Get started free

Figma Feedback to Slack

OtherFree

Description

Figma Feedback to Slack is a FORMLOVA official workflow that starts from a submitted form response and turns review, classification, notification, record keeping, and follow-up into one repeatable operating flow. Run the prompt in a connected AI chat to review the responses and carry out the supported actions.

3 steps

  1. 1

    Read the new response

    At chat execution, confirm the target responses, dates, and evidence. Ask when required information is missing.

  2. 2

    Decide the next action

    Decide the next action from the response, score, date, or category.

  3. 3

    Apply to operations

    Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.

    Figma

Setup steps

Setup Steps

This workflow includes external service integrations. Follow the steps below to set it up.

  1. 1

    Read the new response

    At chat execution, confirm the target responses, dates, and evidence. Ask when required information is missing.

    Integration: FORMLOVA
  2. 2

    Decide the next action

    Decide the next action from the response, score, date, or category.

    Integration: FORMLOVA
  3. 3

    Apply to operations

    Confirm access, targets, and copy before execution. Keep results separate from schedules and append business tags or notes while preserving existing values.

    Integration: Figma

Prompt Example

Goal: Organize design feedback with Figma context and share it with the team in Slack. Fields: Respondent email address and Response body. Extract target screen, location, priority, and requested change. Rules: Turn feedback that maps to a Figma area into comments, and share vague feedback as clarification items in Slack. Actions: Create a comment only if the connected Figma MCP provides comment writing and access to the specified file; otherwise prepare a review note. Post summary, screen, priority, and next action through Slack MCP. Distinguish created comments from prepared notes and verify each result. Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them. Records: update_response accepts only new / in_progress / resolved / spam for status. Use status="in_progress" for new open work; do not reopen existing resolved/spam responses, and use resolved only when the work is verified complete. Immediately before changing business tags or notes, read their current values with search_responses. Pass the deduplicated full set of existing plus added tags (at most 20 tags, 50 characters each), or the full existing notes with the addition appended. If current values cannot be read or limits would be exceeded, ask instead of overwriting. Keep schedules and drafts separate from verified sends, writes, and attendance. External connections: Separate Figma / Slack MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.

For you

steps
3 steps
Required plan
Free
Required integrations
FORMLOVAFigma

What this workflow solves

Form responses arrive, but sharing design feedback with Figma context in Slack still depends on manual checking, causing delayed or missed follow-up.

Best for

  • external tool workflows
  • operational note taking

Expected outcome

When you run the prompt in chat, each reviewed response moves into a clear sharing design feedback with Figma context in Slack state, so the team can focus on the next required action.

Setup notes

  • Connect FORMLOVA MCP in your AI client and confirm permission to read and update responses for the target form.
  • Execution: Run this reusable prompt in an AI chat connected to FORMLOVA. Pasting it does not start continuous monitoring or recurring execution. Only settings saved and verified through actual tools run automatically. Request missing targets, dates, or evidence instead of inventing them.
  • Separate Figma / Slack MCP connections and write access to the specified destinations are required. If the connected MCP lacks a required operation, stop at a draft or review note. External service terms are separate from the FORMLOVA plan.
  • Response review, organization, and ordinary individual replies are available on Free. Check AI client and external service terms separately.
  • Business labels are not response statuses. Read current tags/notes immediately before updating and preserve them when appending; tags allow at most 20 values of 50 characters each. Ask if values cannot be read or limits would be exceeded.

FAQ

Can this work with an existing form?

Yes. Map the existing response fields to the required slots and adjust the notification or record destination.

More in this category

Response to Notion Database

OtherFree

An official workflow for saving form responses into a Notion database.

3 steps
Back to workflows