Skip to main content

Make Waves ’26 Step into AI’s glass box. Prague, 19–20 Oct.

Register now (opens in a new tab)
PiAPI/Flux.1
Tally

Connect PiAPI/Flux.1 and Tally

Explore ready-made PiAPI/Flux.1 and Tally templates and start automating in minutes.

Get started free

Create a custom workflow

Integrate PiAPI/Flux.1 with Tally and automate the work that moves between them — no code required.

Create a custom workflow

Every automation starts with a trigger and an action. Select one from each app to generate a workflow tailored to your needs.

Tally
Trigger: Watch New Responses
PiAPI/Flux.1
Action: Select an action
1. Select a trigger

  • Triggers when a new form response is submitted.

2. Select an action

  • Expands the boundaries of an image. The user uploads an image, and the system generates new background or scenery based on the original content. Suitable for extending the image’s view into a broader scene.

  • Creates a new variation of an image based on the original input.

  • Generates a new image based on an input image. The user uploads an existing image, and the system modifies or transforms it to generate a new version.

  • Generates a modified image based on the LoRA model.

  • Creates an image based on a text description.

  • Creates an image based on a text description using LoRA for fine-tuned generation.

  • Generates an image using ControlNet and LoRA.

  • Performs an arbitrary authorized API call.

  • Removes the background from an image, leaving a transparent or solid-color background.

  • Restores a damaged image. The user uploads an image with some parts missing or damaged, and the system fills in these gaps based on the user's description.

Select a trigger and an action

Create workflow (opens in a new tab)

Triggers and actions

Explore what you can automate between PiAPI/Flux.1 and Tally.

Extend an Image
Expands the boundaries of an image. The user uploads an image, and the system generates new background or scenery based on the original content. Suitable for extending the image’s view into a broader scene.
Action
Generate a Variation of an Image
Creates a new variation of an image based on the original input.
Action
Generate an Image from an Image
Generates a new image based on an input image. The user uploads an existing image, and the system modifies or transforms it to generate a new version.
Action
Generate an Image from an Image with LoRA
Generates a modified image based on the LoRA model.
Action
Generate an Image from Text
Creates an image based on a text description.
Action
Generate an Image from Text with LoRA
Creates an image based on a text description using LoRA for fine-tuned generation.
Action
Generate an Image with ControlNet and LoRA
Generates an image using ControlNet and LoRA.
Action
List Fields Definitions
Lists all field definitions for the selected form.
Search
Make an API Call
Performs an arbitrary authorized API call.
Action
Load more

Support

FAQs

Everything you need to know about Make. Can't find the answer you're looking for? Please chat to our team.

Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.

A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.

Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.

Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.