Forms overview
Dailybot Forms collect structured information from team members or connected systems. Use a form when you need questions answered once or on demand, a record of each submission, and a clear next step for the response.
Forms and check-ins serve different jobs
- A form collects a response when a person or system submits it. Common examples include surveys, polls, access requests, release reviews, intake forms, and approvals.
- A check-in asks selected participants questions on a schedule and compiles their answers into a report.
Choose the surface that matches how the information enters Dailybot. A form can also start an automation after a response is received.
What you use forms for
| Kind | Typical use |
|---|---|
| Polls and surveys | One or few questions with fixed choices; one-time team surveys. |
| Planning poker | Estimation rounds with hidden votes until reveal. |
| Custom data | Sign-ups, intake, or lightweight datasets your team fills in over time. |
| Coffee chat | Pair people for informal 1:1s across remote teams. |
How the lifecycle works
- Create a form from scratch or a template; set question types (text, number, choice, etc.).
- Distribute by selecting participants and sending via DM from Dailybot or sharing a link.
- Collect responses as each person submits; partial progress is visible to owners where permissions allow.
- View results in the form summary or export; planning poker adds reveal and comparison steps.
Forms complement check-ins: check-ins are recurring rituals; forms are ad hoc or session-based data collection. For setup detail, see Creating a form; for limits, see Form expiration and response limits.
Build and share a form
Open Forms in the Dailybot web app to create and configure a form. Add the questions required for the request, review who should have access, and choose how responses should be handled. Share the form through the destinations available to your organization.
Before publishing, submit a test response. Confirm that required questions behave as expected and that the people who need the result can access it.
Add approvals or workflow states
Use an approval flow when a response needs an approve-or-reject decision from designated people. See Forms with approval flows for the setup flow.
Use workflow states when a response needs to move through more than one stage. The available configuration is shown in the form builder. Automations can connect form events to supported actions, such as notifying a destination or starting another saved flow.
Use forms from code or an agent
The public API and Dailybot CLI support documented form operations for integrations and automated work. The agent skill pack can guide a compatible coding agent through supported form tasks.
Use the Forms API reference for current endpoints, fields, permissions, and examples. Use the agent skill reference for the supported skill and CLI surface. Keep API keys and other credentials in a secret manager rather than in form content or source control.
Review access before collecting sensitive data
Only ask for information your workflow needs. Review form access, response visibility, owners, and approvers before sharing the form. If a process handles sensitive or regulated data, confirm your organization’s requirements before collecting it.