add_recipients
ChatGPTAdd people to a request. Each person gets a personal link. Known values go in "prefill" (keys are field ids), and the person only confirms or fixes them. For people who know the user and expect the email, for example speakers, clients, staff, or members. Give a list, or paste CSV text with a header row: an "email" column, an optional "name" column, and columns named like field ids or labels for prefill. By default an invite email goes to each new person. The same email again updates the prefill and keeps the link. On a form, this makes it a request: it keeps its open link and its answers, and AllBack starts to remind the people you add. Then use the request tools for it.
clear_test_answers
ChatGPTDelete the test answers (from the test_link) of a request or a form, with their files. Real answers stay. Use it before the real send, so the numbers start at zero.
close_form
ChatGPTClose a form, so its open link stops taking answers. Every answer stays. Set reopen to true to open it again.
close_request
ChatGPTClose a request, so its links stop taking answers and no more reminders go out. Every answer stays. Set reopen to true to open it again.
create_form
ChatGPTcreate_meeting_poll
ChatGPTMake a poll to find a time that works for everyone, as a draft: a title, the days or times to vote on, and optionally the people to invite. Nothing goes out yet. Each option is a whole day, or a start time on a day. People vote yes, if needed, or no, and see the times in their own time zone. Show the user manage_url to check it, then call send_meeting_poll. To change a draft, call it again with poll_id. Fields you leave out stay as they are; options and people replace the whole list.
create_request
ChatGPTcreate_signup_sheet
ChatGPTMake a sign-up sheet as a draft. mode "slots": volunteer shifts or tasks, each with a number of places and an optional day and time. mode "potluck": dishes to bring, each with a number of places, and people write what they bring. Nothing goes out yet. Show the user manage_url to check it, then call send_signup_sheet. To change a draft, call it again with sheet_id. Fields you leave out stay as they are; slots and people replace the whole list.
export_form_results
ChatGPTGet all answers of a form as CSV (one row per answer, one column per field) and a download link. File answers are links that work for 7 days.
export_request_results
ChatGPTGet all answers of a request as CSV (one row per person, one column per field) and a download link. File answers are links that work for 7 days.
get_activity
ChatGPTAnswer "what happened today?" or "anything new?": the latest opens, answers, documents read, invites, and reminders, newest first. Give request_id or form_id for one request or form. Leave both out for the open requests and forms of the user together.
get_answers
ChatGPTRead the answers of a request or a form here, to summarize them, compare them, or answer "what did Anna say?". Each item is one person (or one open-link answer): name, email, done, and the answers by field id. The fields list gives the label of each id. People who started but did not send are in it too, with done: false and the answers they have so far. Give email for one person. Long lists come in pages: call again with next_offset. For a CSV file, use export_request_results or export_form_results.
get_form
ChatGPTGet a form: its JSON, the open link, if it is open or closed, and the number of answers. Use it before update_form, or to answer "what is the link?" and "how many answers?".
get_form_insights
ChatGPTShow how a form performs: answers, answers each day, the finish rate, the question where people stop, and plain suggestions to get more answers.
get_meeting_poll
ChatGPTWithout poll_id: the user's meeting polls. With poll_id: each option with its yes, if needed, and no votes, the best options, and the votes of each person. Use it for "which time works best?" and "who did not vote?".
get_request
ChatGPTGet the form JSON and the settings of a request: due date, invite message, reminders, email settings, the open link (or null when it is off), status, and a preview link for each ending. Use it before update_request.
get_request_insights
ChatGPTShow how a request performs: the funnel (invited, opened, started, done), the question where people stop, how long the form takes, which email (invite or reminder N) came before each answer, document read rates, and plain suggestions to get more answers.
get_secret_santa
ChatGPTWithout group_id: the user's Secret Santa groups. With group_id: the group, and for each person if they opened the link and added a wish list. It never shows who gives to whom.
get_signup_sheet
ChatGPTWithout sheet_id: the user's sign-up sheets. With sheet_id: each slot with its places and the people who took it (and what they bring), and who on the list did not sign up.
get_status
ChatGPTAnswer "who is still missing?" for a request: each person is done, opened but not done (with what is still missing), or not opened. People who still owe answers come first. It also shows the next reminder, and who read each document.
list_forms
ChatGPTList the user's forms, with the number of answers each. For requests, use list_requests.
list_requests
ChatGPTList the user's requests, with the number of people who are done, started, and not started. For forms, use list_forms.
list_templates
ChatGPTList the ready-made templates: speaker details, client onboarding, policy sign-off, event RSVPs, feedback surveys, and more. Each one has a slug, its kind (request for a list of people, form for one open link), and its first questions. Give slug to get the full form JSON of one template, to change it and pass it as form. Or pass the slug as template to create_request or create_form.
pick_meeting_time
ChatGPTPick the final time of an open meeting poll. The poll closes, and every person with an email gets the time and a calendar file. Get the option_id from get_meeting_poll. Ask the user before you call it: the emails cannot be taken back.
preview_emails
ChatGPTShow the emails of a request as a person gets them: the invite, and the next reminder with its time. Use it when the user asks "what will people get?" before add_recipients, or before send_reminders. Without people on the list, it shows a sample person. To change the text, call update_request with a new message.
send_feedback
ChatGPTSend feedback about AllBack to the AllBack team. The team reads each one and uses it to fix and improve the tools. Call it on your own when: a tool fails in a way that its error does not explain, a tool does something different from its description, you needed several tries to get something right, or the user asks for something that AllBack cannot do. Also call it when the user asks you to send feedback. Send one feedback for each problem, not one for each failed call. Do not send it for errors that you fixed by following the error message. In message, write what you tried, what happened (the exact error), and what you expected. Do not put answers, names, or email addresses of the people on a list in message. After you send it, tell the user in one short line.
send_meeting_poll
ChatGPTOpen a meeting poll draft: it gets an open_link that anyone can use to vote, and each person on the list gets an invite email with their own link. Give the user the open_link to share in a chat or an email. Ask the user before you call it: the emails cannot be taken back.
send_reminders
ChatGPTSend a reminder email now to the people in a request who have not finished. Nobody gets two reminders within 12 hours. Optionally give a short friendly note, or limit it to some emails.
send_secret_santa
ChatGPTDraw the names of a Secret Santa draft and email each person their link. Each person sees only their own match. AllBack reminds people to add a wish list, tells each Santa when the wish list of their match is ready, and sends a note on the exchange day. Ask the user before you call it: the emails cannot be taken back. A user can send at most 5 groups a day.
send_signup_sheet
ChatGPTOpen a sign-up sheet draft: it gets an open_link that anyone can use to sign up, and each person on the list gets an invite email with their own link. Give the user the open_link to share. AllBack sends each person a confirmation and a reminder before their slot. Ask the user before you call it: the emails cannot be taken back.
update_form
ChatGPTChange a form: the questions and endings (send the full new form JSON, in the format of create_form), the title, or the email settings. The open link stays the same. Answers stay for the fields that stay.
update_request
ChatGPTChange a request: the form (send the full new form JSON, in the format of create_request), the title, the due date, the invite message, the reminders, or the open link. Use it for asks like "make it like Typeform" or "add a T-shirt size question". People keep their answers for fields that stay. Set open_link: true to add one link that anyone can fill, next to the personal links, and get the link back in open_link (the same link each time). Set open_link: false to turn it off. Example: the request goes to 20 known speakers, and the co-host posts the open link in Slack for speakers who are not on the list. Open-link answers get no prefill and no reminders, and they are not in get_status. They are in export_request_results.
