Bring form details into the review moment
Have Notis fetch the details of a known Byteforms form when a task reaches review, so the form's purpose and structure are easier to recall.
Trigger
Task Moved to Section
Triggers when a task is moved to a section in a project.
Action
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
Why this helps
Reviewers may need to leave the project to look up what a form asks for or how it relates to the work.
- Make form details available at a project review point.
- Reduce context switching to locate form information.
- Support more informed review handoffs.
Setup
Build it in a few focused steps.
- 1Connect Asana and Byteforms once in the Notis portal.
- 2Create an automation in the portal or tell Notis from any channel what outcome you want.
- 3In one instruction, ask Notis to retrieve the relevant Byteforms form details using its known identifier and summarize them for review.
- 4Choose Asana's Task Moved to Section trigger and select where run reports should go.
- 5Test with one real task and verify the returned form details in the report.
Questions about this workflow
Where does the form identifier come from?
Provide the relevant form identifier in your instruction or other context available to Notis. The listed action retrieves a form by its unique identifier.
Can Notis search forms by name with this action?
Get Form By ID requires the form's unique identifier. Use Get all forms if you need to retrieve the full list.
Does this change the form?
No. Get Form By ID retrieves details and does not edit the form.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Asana to Byteforms. A trigger fires from one place; an action lands in another.
Asana triggers
Byteforms actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create form
Tool to create a new form. use when you need to define and store a form structure.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Form
Tool to delete a form by its id. use when you need to remove an existing form permanently.
Attachment Added to Task
Triggers when an attachment is added to a task.
Get all forms
Tool to fetch all forms created by the authenticated user. use after authentication to list existing forms.
New Comment on Task
Triggers when a comment is added to a task in a project.
Get Form By ID
Tool to retrieve a specific form using its id. use when you need to fetch form details by providing the form's unique identifier.
New Task Created
Triggers when a new task is created in a project.
Get Form Responses
Tool to retrieve responses for a specific form with optional pagination and filtering. use when the form has collected submissions and you need to navigate large result sets.
Task Moved to Section
Triggers when a task is moved to a section in a project.
Tag Added to Task
Triggers when a tag is added to a task. Note: Asana's event structure is inverted for tag events — the resource is the task and the parent is the tag. So parent.gid gives the tag GID.
Task Updated
Triggers when a task is updated in a project.
Connect any two apps with Notis in the middle.
Asana and Byteforms, or any other combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Byteforms.