Act! 365 integration. Manage Contacts, Groups, Opportunities, Tasks, Users. Use when the user wants to interact with Act! 365 data.
Install with Tessl CLI
npx tessl i github:membranedev/application-skills --skill act-36575
Quality
70%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/act-365/SKILL.mdAct! 365 is a simplified CRM software designed for small businesses. It helps users manage contacts, sales opportunities, and marketing activities in a single platform. It's typically used by sales and marketing teams in smaller organizations.
Official docs: https://help.act.com/hc/en-us
This skill uses the Membrane CLI to interact with Act! 365. Membrane handles authentication and credentials refresh automatically — so you can focus on the integration logic rather than auth plumbing.
Install the Membrane CLI so you can run membrane from the terminal:
npm install -g @membranehq/climembrane login --tenantA browser window opens for authentication.
Headless environments: Run the command, copy the printed URL for the user to open in a browser, then complete with membrane login complete <code>.
membrane search act-365 --elementType=connector --jsonoutput.items[0].element?.id, then:
membrane connect --connectorId=CONNECTOR_ID --jsonWhen you are not sure if connection already exists:
membrane connection list --jsonconnectionIdWhen you know what you want to do but not the exact action ID:
membrane action list --intent=QUERY --connectionId=CONNECTION_ID --jsonThis will return action objects with id and inputSchema in it, so you will know how to run it.
| Name | Key | Description |
|---|---|---|
| List Contacts | list-contacts | No description |
| List Companies | list-companies | No description |
| List Opportunities | list-opportunities | No description |
| List Users | list-users | No description |
| List Products | list-products | No description |
| List Groups | list-groups | No description |
| List Tasks | list-tasks | No description |
| List History | list-history | No description |
| List Notes | list-notes | No description |
| Get Contact | get-contact | No description |
| Get Company | get-company | No description |
| Get Opportunity | get-opportunity | No description |
| Get User | get-user | No description |
| Get Product | get-product | No description |
| Get Group | get-group | No description |
| Get Task | get-task | No description |
| Get History | get-history | No description |
| Get Note | get-note | No description |
| Create Contact | create-contact | No description |
| Create Company | create-company | No description |
membrane action run --connectionId=CONNECTION_ID ACTION_ID --jsonTo pass JSON parameters:
membrane action run --connectionId=CONNECTION_ID ACTION_ID --json --input "{ \"key\": \"value\" }"When the available actions don't cover your use case, you can send requests directly to the Act! 365 API through Membrane's proxy. Membrane automatically appends the base URL to the path you provide and injects the correct authentication headers — including transparent credential refresh if they expire.
membrane request CONNECTION_ID /path/to/endpointCommon options:
| Flag | Description |
|---|---|
-X, --method | HTTP method (GET, POST, PUT, PATCH, DELETE). Defaults to GET |
-H, --header | Add a request header (repeatable), e.g. -H "Accept: application/json" |
-d, --data | Request body (string) |
--json | Shorthand to send a JSON body and set Content-Type: application/json |
--rawData | Send the body as-is without any processing |
--query | Query-string parameter (repeatable), e.g. --query "limit=10" |
--pathParam | Path parameter (repeatable), e.g. --pathParam "id=123" |
membrane action list --intent=QUERY (replace QUERY with your intent) to find existing actions before writing custom API calls. Pre-built actions handle pagination, field mapping, and edge cases that raw API calls miss.d19a82b
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.