Connect Sprig to Flodesk

Both apps 34Sprig 19Flodesk 15

• Trigger
  New Study

  Triggers when a new study (survey) is created in Sprig.

• Trigger
  New Survey Response

  Triggers when a new answer to a Sprig survey question is submitted.

• Action
  Create Invitations

  Creates a batch of single-use invitation links for a Sprig survey.

• Action
  Create Survey

  Creates a draft shareable Sprig survey. Questions are added separately.

• Action
  Delete Draft Study

  Deletes a draft Sprig study. Only draft studies can be deleted.

• Action
  Delete Question

  Deletes a question from a Sprig study. Needs the study's current version.

• Action
  Get Question

  Returns one question of a Sprig study, with its options.

• Action
  Get Study

  Returns one Sprig study by its ID, including its current version.

• Action
  Get User

  Returns a Sprig user by user ID, with attributes and tracked events.

• Action
  List Attributes

  Returns the user attributes defined in the Sprig environment.

• Action
  List Events

  Returns the tracked events defined in the Sprig environment.

• Action
  List Invitations

  Returns invitation links of a Sprig survey, filtered by status.

• Action
  List Questions

  Returns the questions of a Sprig study.

• Action
  List Studies

  Returns a page of Sprig studies (surveys), optionally filtered by status or type.

• Action
  List Survey Responses

  Returns exported Sprig survey responses, optionally for one survey.

• Action
  Purge Visitors

  Requests deletion of Sprig users and all their data, by email or user ID (up to 100).

• Action
  Update Study Name

  Renames a Sprig study. Needs the study's current version from Get Study.

• Action
  Upsert User

  Creates or updates a Sprig user by user ID, setting email and attributes.

• Action
  Validate Study

  Checks a Sprig study and returns any issues that would block it from launching.

• Action
  Add custom field

  Creates a new subscriber custom field in your Flodesk account with the label you choose.

• Action
  Add Existing Subscriber to Segment

  Adds an existing Flodesk subscriber to one or more segments and returns the updated subscriber.

• Action
  Add Existing Subscriber to Workflow

  Adds an existing Flodesk subscriber to a workflow, identified by subscriber ID or email address.

• Action
  Add segment

  Creates a new segment in your Flodesk account and returns it.

• Action
  Create/Update Subscriber

  Creates a new Flodesk subscriber, or updates the existing one with the same email address or id, optionally adding them to segments.

• Action
  Find a Subscriber by Email Address

  Looks up a Flodesk subscriber by email address and returns their status, name, segments and custom field values.

• Action
  Get segment

  Returns a single Flodesk segment, including its name, color, type and number of active subscribers.

• Action
  List campaigns

  Returns the email campaigns in your Flodesk account, optionally filtered by status or a search term.

• Action
  List custom fields

  Returns every subscriber custom field defined in your Flodesk account, with each field's key and display label.

• Action
  List segments

  Returns all segments in your Flodesk account, with each segment's name, color, type and active subscriber count.

• Action
  List subscribers

  Returns subscribers in your Flodesk account, optionally filtered by status or segment.

• Action
  List workflows

  Returns the workflows in your Flodesk account, optionally filtered by status (active, paused or draft).

• Action
  Remove Existing Subscriber From Segment

  Removes an existing Flodesk subscriber from one or more segments and returns the updated subscriber.

• Action
  Remove Existing Subscriber From Workflow

  Removes an existing subscriber, identified by subscriber ID or email address, from a Flodesk workflow.

• Action
  Unsubscribe Subscriber

  Unsubscribes a subscriber from all of your Flodesk lists so they no longer receive marketing emails, and returns the updated subscriber.

No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.