Basecamp (Independent Publisher)

[aaronmahbuild]

• I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
• I attest that the connector works and I verified by deploying and testing all the operations.
• I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
• I attest that I have added response schemas to my actions, unless the response schema is dynamic.
• I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
• If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.
• I have named this PR after the pattern of "Connector Name (Independent Publisher)" ex: HubSpot Marketing (Independent Publisher)
• Within this PR markdown file, I have pasted screenshots that show: 3 unique operations (actions/triggers) working within a Flow. This can be in one flow or part of multiple flows. For each one of those flows, I have pasted in screenshots of the Flow succeeding.
• Within this PR markdown file, I have pasted in a screenshot from the Test operations section within the Custom Connector UI.
• If the connector uses OAuth, I have provided detailed steps on how to create an app in the readme.md.

---

Basecamp — Independent Publisher Connector

Overview

Basecamp is a project management and team communication platform by 37signals. This connector enables Power Automate and Power Apps to interact with Basecamp projects, to-do lists, messages, schedule entries, and comments — bridging Basecamp workflows with the Microsoft Power Platform.

Publisher

Aaron Mah

Operations (15 total)

#	Operation	Type	Description
1	List Projects	Action	Lists all active projects in the Basecamp account
2	Get Project	Action	Gets details of a specific project, including dock tool IDs
3	List To-do Lists	Action	Lists all to-do lists in a project's to-do set
4	Create To-do List	Action	Creates a new to-do list in a project's to-do set
5	List To-dos	Action	Lists to-do items in a specific to-do list
6	Create To-do	Action	Creates a new to-do item with optional description, assignees, and due date
7	Get To-do	Action	Gets the full details of a specific to-do item
8	Complete To-do	Action	Marks a to-do item as complete
9	List Messages	Action	Lists all messages on a project's message board
10	Create Message	Action	Posts a new message to a project's message board
11	Get Message	Action	Gets the full details of a specific message
12	List Schedule Entries	Action	Lists all entries on a project's schedule
13	Create Schedule Entry	Action	Creates a new event on a project's schedule
14	Get Schedule Entry	Action	Gets the full details of a specific schedule entry
15	Create Comment	Action	Adds a comment to any Basecamp recording (to-do, message, etc.)

Authentication

OAuth 2.0 Authorization Code flow. Basecamp does not use granular scopes — the token inherits the authenticating user's permissions. Users must also provide their Basecamp Account ID (found in the URL: https://3.basecamp.com/{account_id}/...). Detailed OAuth app setup instructions are in the Readme.

Test Results

• 15/15 operations tested successfully via PA APIM gateway
• Swagger validation passed (0 errors, 0 warnings)
• UI click-through completed for all 15 operations in PA test tab
• 3/3 end-to-end scenario flows validated in Power Automate

Test Tab — All Operations (15/15 Passed)

APIM Gateway Test — All Operations Passed

All 15 operations were tested end-to-end through Power Automate's APIM gateway, which is the same backend used by the PA test tab and flows:

#	Operation	HTTP	Status	Notes
1	listProjects	200	✅ Pass	1 project returned
2	getProject	200	✅ Pass	Dock IDs extracted
3	listTodoLists	200	✅ Pass	Lists returned
4	createTodoList	201	✅ Pass	Created successfully
5	listTodos	200	✅ Pass	Empty list on new todo list
6	createTodo	201	✅ Pass	Created with content
7	getTodo	200	✅ Pass	Metadata verified
8	completeTodo	204	✅ Pass	No content (expected)
9	listMessages	200	✅ Pass	Message board queried
10	createMessage	201	✅ Pass	Message posted
11	getMessage	200	✅ Pass	Content verified
12	listScheduleEntries	200	✅ Pass	Schedule queried
13	createScheduleEntry	201	✅ Pass	Event created
14	getScheduleEntry	200	✅ Pass	Times verified
15	createComment	201	✅ Pass	Comment added to todo

Scenario Flows (3/3 Passed)

Three end-to-end flows were built and tested in Power Automate, each exercising the Basecamp dock-navigation pattern (Get Project → filter dock array → extract tool ID → call operation) with Teams notifications.

Scenario 1: Task Request → Basecamp To-do
Creates a to-do in Basecamp from a task request and posts confirmation to Teams. Exercises: getProject, listTodoLists, createTodo.

Scenario 2: Announcement → Message Board
Posts an announcement to a Basecamp message board and notifies Teams. Exercises: getProject, createMessage.

Scenario 3: Weekly Schedule Digest
Retrieves upcoming schedule entries from Basecamp, composes a digest, and posts to Teams. Exercises: getProject, listScheduleEntries.

Known Limitations

• Pagination: Basecamp uses Link header pagination; list operations return the first page only
• No update operations: PUT endpoints require all fields (omitting clears); deferred to avoid data loss
• Rate limit: 50 requests per 10-second window; PA handles 429 retries automatically
• Free plan: Limited to 1 project

[vmanoharas]

Hi @aaronmahbuild,

Thank you for your interest in submitting the Basecamp connector under the Independent Publisher (IP) program.

After review, we’re unable to proceed with this submission because Basecamp already exists as an official Microsoft connector in the Power Platform connector catalog.

As per the Independent Publisher certification policy, new Independent Publisher connectors cannot be created for services that already have an existing Microsoft or certified connector.
This requirement is documented publicly here: https://learn.microsoft.com/en-us/connectors/custom-connectors/certification-submission-ip#step-1-verify-connector-isnt-already-built