Tally

!Tally

Manage Tally forms, submissions, respondents, fields, and form workflows from chat via the Tally API.

This skill uses ClawLink for hosted connection flows and credentials so you do not need to configure Tally API access yourself.

Setup in 3 Steps

How It Works

┌─────────────────┐     ┌──────────────┐     ┌──────────────────┐
│   OpenClaw      │────▶│   ClawLink   │────▶│   Tally API      │
│   (User Chat)   │     │   (OAuth)    │     │                  │
└─────────────────┘     └──────────────┘     └──────────────────┘
         │                       │                       │
         │  1. Install Plugin    │                       │
         │  2. Pair Device       │                       │
         │  3. Connect Tally     │                       │
         │                       │  4. Secure Token      │
         │                       │  5. Proxy Requests    │
         │                       │                       │
         ▼                       ▼                       ▼
   ┌──────────┐           ┌──────────┐           ┌──────────┐
   │  SKILL   │           │ Dashboard│           │  Tally   │
   │  File    │           │ Auth     │           │  Account │
   └──────────┘           └──────────┘           └──────────┘

Install

Install the verified ClawLink plugin from ClawHub. After the user confirms, complete the full setup so ClawLink tools are visible in the next OpenClaw chat.

openclaw plugins install clawhub:clawlink-plugin
openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json
openclaw gateway restart

Then tell the user: "OpenClaw has been restarted. Send /new as a standalone message to start a fresh chat, then ask for Tally again."

Quick Start

# List all forms
clawlink_call_tool --tool "tally_list_forms" --params '{}'

# Get form details
clawlink_call_tool --tool "tally_get_form" --params '{"form_id": "FORM_ID"}'

# List submissions for a form
clawlink_call_tool --tool "tally_list_submissions" --params '{"form_id": "FORM_ID"}'

Authentication

All Tally tool calls are authenticated automatically by ClawLink using the user's connected Tally account OAuth token.

No API token is required in chat. ClawLink stores the OAuth token securely and injects it into every Tally API request on the user's behalf.

Getting Connected

1. Install the ClawLink plugin (see Install above).
2. Pair the plugin with clawlink_begin_pairing if it is not configured yet.
3. Open https://claw-link.dev/dashboard?add=tally and connect Tally.
4. Call clawlink_list_integrations to verify the connection is active.

Connection Management

List Connections

clawlink_list_integrations

Response: Returns all connected integrations. Look for tally in the list.

Verify Connection

clawlink_list_tools --integration tally

Response: Returns the live tool catalog for Tally.

Reconnect

If Tally tools are missing or the connection shows an error:

1. Direct the user to https://claw-link.dev/dashboard?add=tally
2. After they confirm, call clawlink_list_integrations to verify
3. Then call clawlink_list_tools --integration tally

Security & Permissions

• Access is scoped to forms and data accessible to the connected Tally account.
• Write operations (create form, delete submission) require explicit user confirmation.
• Submission data may contain personal information — handle in accordance with privacy best practices.
• Confirm before making bulk changes to form settings or deleting submissions.

Tool Reference

Forms

Submissions

Respondents

Fields

Form Workflows

Notifications

Code Examples

List all forms

clawlink_call_tool --tool "tally_list_forms" \
  --params '{}'

Get form with fields

clawlink_call_tool --tool "tally_get_form" \
  --params '{
    "form_id": "FORM_ID"
  }'

List submissions for a form

clawlink_call_tool --tool "tally_list_submissions" \
  --params '{
    "form_id": "FORM_ID",
    "limit": 20
  }'

Get a specific submission

clawlink_call_tool --tool "tally_get_submission" \
  --params '{
    "form_id": "FORM_ID",
    "submission_id": "SUBMISSION_ID"
  }'

Submit a form response

clawlink_call_tool --tool "tally_submit_form" \
  --params '{
    "form_id": "FORM_ID",
    "fields": {
      "EMAIL": "respondent@example.com",
      "MESSAGE": "This is my response"
    }
  }'

Get respondent list

clawlink_call_tool --tool "tally_list_respondents" \
  --params '{
    "form_id": "FORM_ID",
    "limit": 50
  }'

Discovery Workflow

1. Call clawlink_list_integrations to confirm Tally is connected.
2. Call clawlink_list_tools --integration tally to see the live catalog.
3. Treat the returned list as the source of truth. Do not guess or assume what tools exist.
4. If the user describes a capability but the exact tool is unclear, call clawlink_search_tools with a short query and integration tally.
5. If no Tally tools appear, direct the user to https://claw-link.dev/dashboard?add=tally.

Execution Workflow

┌─────────────────────────────────────────────────────────────┐
│  READ OPERATIONS (Safe)                                     │
│  list → get → describe                                      │
│                                                             │
│  Example: List forms → Get submissions → Review responses  │
└─────────────────────────────────────────────────────────────┘
                              │
                              ▼
┌─────────────────────────────────────────────────────────────┐
│  WRITE OPERATIONS (Require Confirmation)                    │
│  describe → preview → confirm → call                        │
│                                                             │
│  Example: Preview form creation → User approves → Create    │
└─────────────────────────────────────────────────────────────┘

1. For unfamiliar tools, ambiguous requests, or any write action, call clawlink_describe_tool first.
2. Use the returned guidance, schema, whenToUse, askBefore, safeDefaults, examples, and followups to shape the call.
3. Prefer read, list, and get operations before writes when that reduces ambiguity.
4. For writes or anything marked as requiring confirmation, call clawlink_preview_tool first.
5. Execute with clawlink_call_tool. Pass confirmation only after the preview matches the user's intent.
6. If the tool call fails, report the real error. Do not invent results or restate the failure as a missing capability unless the live catalog supports that conclusion.

Notes

• Form IDs are required for most operations — use tally_list_forms to discover form IDs.
• Submissions contain field values mapped by field ID (not field label).
• Deleted forms and submissions cannot be recovered — always confirm before deleting.
• Field IDs in submissions match the internal field identifiers, not visible labels.
• Tally's API is read-focused for submissions — form creation and modification capabilities vary by plan.

Error Handling

Troubleshooting: Tools Not Visible

1. Check that the ClawLink plugin is installed:

```bash

openclaw plugins list

```

1. If the plugin is installed but tools are missing, tell the user to send /new as a standalone message to reload the catalog.
2. If a fresh chat does not help, run:

```bash

openclaw config set tools.alsoAllow '["clawlink-plugin"]' --strict-json

openclaw gateway restart

```

1. After restart, tell the user to send /new again and retry.

Resources

• Tally API Documentation
• Tally Developer Docs
• ClawLink: https://claw-link.dev/?utm_source=clawhub&utm_medium=referral&utm_content=tally-forms
• ClawLink Docs: https://docs.claw-link.dev/openclaw
• ClawLink Verification: https://claw-link.dev/verify

Powered by ClawLink — an integration hub for OpenClaw

!ClawLink Logo