Tally integration

What it does

The Tally integration lets your agency turn a client's forms into the front door of an automated workflow. Connect a client's Tally account once and you can list and inspect every form, pull the form's question metadata, page through submissions with status and date filters, fetch a single submission with all of its responses, and enumerate workspaces. A FORM_RESPONSE webhook trigger turns every new submission into a workflow run, so the next step (CRM upsert, Slack notification, billing kickoff) runs the moment a respondent hits Submit.

Connect a Tally account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Tally and click Connect.
3. Sign in to the Tally account you want to manage on behalf of your client.
4. Open Settings, choose API keys, and click Create API key. Copy the value immediately; Tally does not show it again.
5. Paste the key into TaskJuice and save. The connection is ready to use in any workflow.

A Tally API key inherits the permissions of the user who created it. If the user is later removed from the organization, the key is deactivated and TaskJuice surfaces a 401 on the next workflow run so you can rotate the credential.

Triggers

• tally/form-response fires when a respondent submits a form. The payload includes the event id, the form id and name, the submission and respondent ids, and an array of answered fields with key, label, type, and value.

Actions

• tally/list-forms lists forms in the connected account with page-based pagination.
• tally/get-form retrieves a single form by id with its settings and all blocks.
• tally/list-form-questions returns a form's questions with their type, title, and field metadata.
• tally/list-submissions lists submissions for a form with status, date-range, and cursor filters, paged via page and limit.
• tally/get-submission fetches a single submission by id along with the form's question metadata.
• tally/list-workspaces lists workspaces in the connected account with their members and pending invites.

Known limitations

• Tally limits API traffic to 100 requests per minute per key. The action engine retries 429 responses with backoff; high-volume submission backfills should pace requests with a downstream throttle.
• API keys are scoped to the user that issued them. Removing that user from the Tally organization deactivates every key they created, which surfaces in TaskJuice as a 401 on the next call.
• Tally webhooks emit a single event type, FORM_RESPONSE, signed with HMAC-SHA256 over the raw request body and sent base64-encoded in the Tally-Signature header. Configure the webhook in Tally with a signing secret and paste the same secret into the trigger; the platform verifies every inbound POST before activating the workflow.
• Submission previewUrl and pdfUrl are signed URLs with embedded access tokens. Treat them as sensitive when forwarding them downstream.