Creating To-Dos in Basecamp is a simple task with the “Basecamp: Create To-Do” steptype. Use this steptype to automatically pull information from your support ticket or record, and populate fields on To-Dos created in Basecamp.
Agents will be prompted to link their Basecamp account the first time they run a Basecamp step in a Flow.

​
Title

The title appears in Sidekick when your team reaches this step in the Flow. Use this field to describe what type of change you want to file in Arena and why.

​
Automatically Complete Step when Created?

Check this box to immediately create the Change in Arena when your team reaches this step. If checked your team won’t have the chance to make edits manually, so you’ll need to fully build out this steptype in Flow Builder.

​
Project & List Selection

These options cannot be modified in Sidekick. The Project and List you select here will be used for every To-Do created with this steptype.

​
Basecamp Project

Use this dropdown to select the Basecamp Project where the new To-Do will be created.

​
To-Do List

After selecting a Project, use this dropdown to select the specific To-Do List within that Project where the new To-Do will be created.

​
To-Do Content

Sets the Title and Description of the new To-Do in Basecamp.

​
Scheduling

Here, you can set the Start Date and Due Date for the new To-Do in Basecamp.

​
Assignment & Notifications

After selecting a Project, you can select Assignees and Completion Subscribers for the To-Do being created. Additionally, you can configure the option to send a notification email to the assignees when the To-Do is created.
In all of the text fields above, you can use the button to pull in variables from other systems, as long as you’ve set up that separate integration in FlowEQ.Each field also has the following options:
  • Hidden?
    • Checking this box will hide this field so that it won’t appear in Sidekick. This is useful when you know what the value should be already and the agent doesn’t have to double-check/edit this field each time.
  • Manual?
    • This will make the field editable to the Sidekick user. This is perfect if you want the agent to type in a value manually, like a product serial number or SKU.
  • Required?
    • If checked, this field will require a value written to it before the Sidekick user can proceed with the Flow. That field value can be written by hard coding it in the step configuration, by writing a variable from another system, or by the agent entering data manually. It doesn’t matter how the data is written to the field as long as it’s not empty.