> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/integrations/catalog/tally.md).

# Tally

Work with Tally forms and submissions.

## Connectors

Choose the connector that matches your authentication method. The options below use the names shown in StackAI.

| Connector | Authentication |
| --------- | -------------- |
| Tally     | API Key        |

### Tally

Connect to Tally to read forms and manage form submissions.

#### Set up in Tally

1. Prepare the Tally account or service that the workflow will access. Grant access to the required resources and operations.
2. **API Key:** Create a user API key under Tally Settings > API keys.

#### Set up in StackAI

1. Open **Settings → Connections**, add a connection, and select **Tally**.
2. Enter the credentials and connection details in the fields below.
3. Save the connection and check its connection status. Select this saved connection when configuring an action or feature that uses it.

**Connection fields**

| StackAI field | Required | What to enter                                                                                                       |
| ------------- | -------- | ------------------------------------------------------------------------------------------------------------------- |
| API Key       | Yes      | Create a user API key under Tally Settings > API keys. [Provider instructions](https://tally.so/settings/api-keys). |

### Verify the connection

Check that the connection is healthy. Then run a read operation against a resource the connected account can access. A successful connection check confirms authentication; it does not guarantee permission for every action.

If access is denied, check the credential or OAuth permissions, the selected account or environment, and access to the specific resource. Update expired credentials or reconnect after permissions change.

## Use an action

1. Add the required **Tally** action to the workflow.
2. Select a connection when the action requests one.
3. Complete the required fields. Use the reference picker when a value comes from another workflow step.
4. Run the workflow and inspect the action’s output. Check the result before using it in a later step.

## Actions

### List Forms

List forms available to the connected Tally user.

#### Inputs

| Field           | Type    | Required | Description                                                                    |
| --------------- | ------- | -------- | ------------------------------------------------------------------------------ |
| Maximum Results | integer | No       | The maximum number of forms to return. Minimum: 1. Maximum: 500. Default: 100. |
| Starting Page   | integer | No       | The page to start listing from. Minimum: 1. Default: 1.                        |
| Workspace IDs   | string  | No       | Optionally limit forms to comma-separated workspace IDs.                       |

#### Outputs

| Field     | Type          | Description                                            |
| --------- | ------------- | ------------------------------------------------------ |
| Forms     | object\_array | The accessible Tally forms.                            |
| Next Page | integer       | The next page to request, if more forms are available. |

### Get Form Details

Get metadata, settings, and blocks for a Tally form.

#### Inputs

| Field | Type            | Required | Description                                                            |
| ----- | --------------- | -------- | ---------------------------------------------------------------------- |
| Form  | select (string) | Yes      | The Tally form to retrieve. Options load from the selected connection. |

#### Outputs

| Field | Type   | Description                                     |
| ----- | ------ | ----------------------------------------------- |
| Form  | object | The requested Tally form and its configuration. |

### List Form Submissions

List and filter submissions for a Tally form.

#### Inputs

| Field               | Type            | Required | Description                                                                                             |
| ------------------- | --------------- | -------- | ------------------------------------------------------------------------------------------------------- |
| Form                | select (string) | Yes      | The Tally form whose submissions should be listed. Options load from the selected connection.           |
| Submission Status   | select (string) | No       | Return all, completed, or partial submissions. Available values: All, Completed, Partial. Default: all. |
| Maximum Results     | integer         | No       | The maximum number of submissions to return. Minimum: 1. Maximum: 500. Default: 100.                    |
| After Submission ID | string          | No       | Resume after this submission ID.                                                                        |
| Submitted After     | datetime        | No       | Only include submissions on or after this date-time.                                                    |
| Submitted Before    | datetime        | No       | Only include submissions on or before this date-time.                                                   |

#### Outputs

| Field             | Type          | Description                                                 |
| ----------------- | ------------- | ----------------------------------------------------------- |
| Submissions       | object\_array | The matching Tally form submissions.                        |
| Questions         | object\_array | Question definitions for interpreting submission responses. |
| Submission Totals | object        | Counts of all, completed, and partial submissions.          |
| Next Cursor       | string        | The cursor to use when more submissions are available.      |

### Get Submission

Get one Tally form submission by ID.

#### Inputs

| Field         | Type            | Required | Description                                                                         |
| ------------- | --------------- | -------- | ----------------------------------------------------------------------------------- |
| Form          | select (string) | Yes      | The Tally form that owns the submission. Options load from the selected connection. |
| Submission ID | string          | Yes      | The Tally submission to retrieve.                                                   |

#### Outputs

| Field              | Type   | Description                                              |
| ------------------ | ------ | -------------------------------------------------------- |
| Submission Details | object | The submission and the questions needed to interpret it. |

### Delete Submission

Permanently delete a Tally form submission.

#### Inputs

| Field         | Type            | Required | Description                                                                         |
| ------------- | --------------- | -------- | ----------------------------------------------------------------------------------- |
| Form          | select (string) | Yes      | The Tally form that owns the submission. Options load from the selected connection. |
| Submission ID | string          | Yes      | The Tally submission to permanently delete.                                         |

#### Outputs

| Field         | Type    | Description                                 |
| ------------- | ------- | ------------------------------------------- |
| Deleted       | boolean | Whether Tally accepted the deletion.        |
| Form ID       | string  | The form that owned the deleted submission. |
| Submission ID | string  | The deleted submission ID.                  |

## Important behavior

Actions that create, update, send, or delete data can change the connected service. Review their inputs before running them. A retry can repeat an operation; consider this when configuring retries for actions that change data.

The catalog lists the fields and capabilities available in the supplied provider definition. Availability can also depend on your deployment and organization’s Feature Access settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/integrations/catalog/tally.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
