AI Automation Engineer — Creator Partnerships CRM and MCP Integration

Please login or register as jobseeker to apply for this job.

TYPE OF WORK

Part Time

SALARY

$800

HOURS PER WEEK

18

DATE UPDATED

Sep 14, 2026

JOB OVERVIEW

AI AUTOMATION ENGINEER — CREATOR PARTNERSHIPS CRM AND MCP INTEGRATION

Remote | Project-Based With Potential Ongoing Maintenance

6FT CLUB® is a Los Angeles-based men’s confidence and footwear brand. We are looking for an experienced AI Automation Engineer to design and build a creator-partnership management system that can be accessed and operated through Claude, ChatGPT, or another MCP-compatible AI assistant.

This is a hands-on implementation project—not a strategy, prompt-writing, or generic virtual-assistant position.

BUSINESS OBJECTIVE

We work with two categories of creators:

1. Los Angeles-based male models and video creators who can visit our Downtown Los Angeles studio to produce content featuring our height-increase shoes. These shoes must remain at the studio.

2. U.S.-based TikTok, Instagram, Amazon, and UGC creators who can receive our height-increase insoles by mail and create short-form video content remotely.

We want a centralized system that helps us discover, evaluate, contact, manage, and follow up with these creators without relying on disconnected spreadsheets, inbox searches, and manual reminders.

WHAT WE WANT BUILT

The finished system should combine:

* A central creator CRM or database.
* AI-assisted creator qualification and brand-fit scoring.
* Personalized outreach drafting.
* Human approval before important external actions.
* Email sending and reply tracking.
* Follow-up reminders and pipeline management.
* Creator campaign and deliverable tracking.
* An MCP server that allows Claude or ChatGPT to safely access and operate the system.

We are open to practical recommendations regarding the technology stack. Possible tools include Airtable, Notion, Google Sheets, Supabase, Gmail, n8n, Make, Zapier, OpenAI, Anthropic, and custom TypeScript or Python development.

We do not require every tool listed above. We want the simplest secure system that solves the business problem without unnecessary monthly software costs.

CORE WORKFLOW

The system should help us with the following:

1. ADD AND ORGANIZE CREATORS

* Add creators manually, through approved data sources, or by importing a CSV.
* Store the creator’s name, location, platforms, profile links, contact information, follower count, engagement information, content category, rates, sizes, and notes.
* Detect and prevent duplicate creator records.
* Distinguish between LA studio talent and U.S.-based remote UGC creators.

2. EVALUATE BRAND FIT

Use AI and predefined criteria to assess whether a creator matches the 6FT CLUB brand.

Our audience primarily includes men interested in:

* Confidence and self-improvement.
* Dating and social life.
* Men’s style and grooming.
* Fitness and looksmaxxing.
* Career and personal presentation.

Strong creator candidates are generally male, approximately 21–35, and capable of producing natural, contemporary short-form video. Creators with an Amazon Storefront or Amazon video experience are especially valuable.

The AI should provide a fit score with an understandable explanation. It should not make unexplained or irreversible decisions.

3. GENERATE PERSONALIZED OUTREACH

* Create personalized email and direct-message drafts based on each creator’s profile and content.
* Use separate outreach templates for LA studio shoots and mailed-insole collaborations.
* Allow a human to review and edit messages before sending.
* Track when outreach was drafted, approved, sent, answered, or ignored.
* Recommend appropriate follow-up messages.
* Prevent duplicate or excessive outreach.

Email
automation may use approved Gmail integrations. Instagram and TikTok workflows must comply with the platforms’ current APIs, terms, rate limits, and account restrictions.

If direct automated messaging is not officially supported, the system should create a safe manual approval or copy-and-send workflow instead. We do not want browser bots or scraping methods that could place our accounts at risk.

4. MANAGE THE CREATOR PIPELINE

The system should support stages such as:

* Discovered.
* Needs Review.
* Approved for Outreach.
* Contacted.
* Follow-Up Due.
* Responded.
* Negotiating.
* Product Shipment Needed.
* Content in Production.
* Content Delivered.
* Approved.
* Declined.
* Do Not Contact.

We should be able to see which creators require attention and what action should happen next.

5. TRACK CAMPAIGN DETAILS

For each creator, we may need to track:

* Agreed compensation.
* Product and size requested.
* Shipping information.
* Tracking number.
* Content brief.
* Due date.
* Usage rights.
* Revision allowance.
* Completed deliverables.
* Payment status.
* Past performance.
* Whether we would work with the creator again.

MCP REQUIREMENTS

Build an authenticated MCP server that exposes narrowly defined tools to an approved AI client.

Suggested MCP tools include:

* Search creators.
* Add a creator.
* Find duplicate creators.
* Score creator brand fit.
* Show creators awaiting review.
* Draft personalized outreach.
* Show messages awaiting human approval.
* Send an approved email.
* Log a response.
* Update a pipeline stage.
* List overdue follow-ups.
* Create a shipping task.
* Record content delivery.
* Generate a campaign-status summary.

The MCP should not give the AI unrestricted access to the underlying database or email account.

Important actions—such as sending messages, changing payment information, deleting records, or marking an agreement as final—must require human confirmation or be protected by role-based permissions.

REQUIRED DELIVERABLES

PHASE 1: DISCOVERY AND ARCHITECTURE

Before building, provide:

* A workflow diagram.
* Recommended technology stack.
* Expected software subscriptions and monthly costs.
* Available official APIs and their limitations.
* Security and authentication plan.
* Proposed database structure.
* List of MCP tools and their permissions.
* Fixed project estimate and implementation timeline.

PHASE 2: WORKING MVP

Build and demonstrate a functioning system that can:

* Store and search creator records.
* Score creators against our brand criteria.
* Draft personalized outreach.
* Send approved emails.
* Track replies and follow-up dates.
* Update creator pipeline stages.
* Surface outstanding actions.
* Allow Claude or ChatGPT to perform approved actions through MCP.

PHASE 3: TESTING AND HANDOFF

Provide:

* End-to-end testing.
* Error handling and activity logs.
* Duplicate and rate-limit protection.
* Setup and deployment documentation.
* A recorded walkthrough.
* Source code and ownership transfer.
* Credential-rotation instructions.
* At least 30 days of post-launch bug support.
* Clear instructions allowing another developer to maintain the system.

SECURITY REQUIREMENTS

* Use OAuth or properly secured API credentials whenever available.
* Never hard-code passwords or API keys.
* Store secrets in environment variables or an appropriate secrets manager.
* Use least-privilege permissions.
* Maintain logs of AI-initiated actions.
* Include human approval for sensitive or external actions.
* Do not use prohibited scraping, browser bots, purchased accounts, or tools that violate platform terms.
* The business must own the source code, database, automation accounts, and deployment environment.

REQUIRED EXPERIENCE

Applicants should have demonstrable experience with several of the following:

* Building production MCP servers.
* TypeScript, Node.js, or Python.
* OAuth and third-party API integrations.
* Gmail API or Google Workspace automation.
* Airtable, Supabase, or another structured database.
* n8n, Make, Zapier, or comparable workflow platforms.
* AI structured outputs and tool calling.
* CRM or lead-management automation.
* Webhooks, queues, logging, and retry handling.
* Secure credential and permission management.

Experience with influencer marketing, creator CRMs, e-commerce, Shopify, or social-media workflows is a major advantage.

HOW TO APPLY

Begin your application with the words: AI Automation Engineer

Please answer all of the following:

1. Describe one MCP server or AI automation system you personally built. What could it read, and what actions could it take?

2. Which parts of this project would you build with custom code, and which parts would you build with tools such as n8n, Make, Airtable, or Supabase?

3. How would you prevent an AI assistant from a ---------- sending an unapproved email, deleting records, or contacting the same creator twice?

4. How would you handle Instagram and TikTok outreach if their official APIs do not support the required messaging workflow?

5. What database or CRM would you recommend for this project, and why?

6. Provide a simple proposed architecture for the system.

7. Identify the major technical risks or limitations you expect.

8. Provide links, screenshots, repositories, or recorded demonstrations of relevant work. Clearly explain which portions you personally built.

9. Provide your proposed price for the discovery and architecture phase. You may provide a preliminary range for the MVP, but we understand that the final quote may depend on discovery.

10. State your availability and time-zone overlap with Los Angeles.

Generic applications, copied proposals, and applications that do not address the platform and security limitations will not be considered.

SKILL REQUIREMENT
VIEW OTHER JOB POSTS FROM:
SHARE THIS POST
facebook linkedin
  BENCHMARKS  
Loading Time: Base Classes  0.0011
Controller Execution Time ( Jobseekers / Job )  0.0161
Total Execution Time  0.0180
  GET DATA  
No GET data exists
  MEMORY USAGE  
1,536,960 bytes
  POST DATA  
No POST data exists
  URI STRING  
jobseekers/job/AI-Automation-Engineer-Creator-Partnerships-CRM-and-MCP-Integration-1730398
  CLASS/METHOD  
jobseekers/job
  DATABASE:  onlinejobs (Jobseekers:$db)   QUERIES: 13 (0.0055 seconds)  (Hide)
0.0004   SELECT *
                                
FROM exrates
                                WHERE rate_name 
= 'USD-PHP' 
0.0005   SELECT *
FROM `employer_jobs`
WHERE `job_id` = 1730398
 LIMIT 1 
0.0004   SELECT *
FROM `employers`
WHERE `employer_id` = 661274
 LIMIT 1 
0.0003   SELECT COUNT(*) AS `numrows`
FROM `t_thread` `t`
LEFT JOIN `t_thread_misc` `misc` ON `t`.`id` = `misc`.`thread_id`
WHERE `t`.`job_id` = 1730398
AND `misc`.`id` IS NULL 
0.0005   SELECT e.business_name, e.logo, e.website, e.rebill_date, e.date_added member_date, hits, DATEDIFF('2026-09-25',ej.date_added) duration_days, DATEDIFF('2026-09-25',e.rebill_date) duration_rebill, ej.*, e.deactivate FROM employers e, employer_jobs ej WHERE e.employer_id = ej.employer_id AND
                                   ((
e.user_level >= '500' AND ej.date_added <= e.rebill_date)
                                   OR 
e.employer_id = '' OR (ej.date_approved <> '2000-01-01' and DATEDIFF('2026-09-25',ej.date_added) <= 14 ))
                                   AND 
e.deactivate != 1 AND ej.deleted = 0 AND job_id = '1730398' 
0.0003   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `sc` ON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1730398 
0.0007   UPDATE employer_jobs SET hit_counts = '***Sep-14-2026=529***Sep-15-2026=473***Sep-16-2026=230***Sep-17-2026=91***Sep-18-2026=49***Sep-19-2026=27***Sep-23-2026=2***Sep-25-2026=2' WHERE job_id= '1730398'  
0.0005   UPDATE employer_jobs SET monthly_hits = '***Sep-2026=1402' WHERE job_id= '1730398'  
0.0003   SELECT date_sent FROM jobseeker_sent_emails WHERE jobseeker_id = '' AND job_id = '1730398' AND status LIKE 'sent%' ORDER BY id DESC  
0.0004   SELECT *
FROM `employer_jobs_skills` `ejs`
LEFT JOIN `skills_categories` `sc` ON `ejs`.`skill_id` = `sc`.`id`
WHERE `job_id` = 1730398 
0.0004   SELECT COUNT(*) AS `numrows`
FROM `employer_jobs`
WHERE `employer_id` = '661274'
AND `date_added` >= '2022-06-08' 
0.0004   select * from teasers 
0.0003   SELECT * FROM skill_categories WHERE skill_cat_id='' 
  HTTP HEADERS  (Show)
  SESSION DATA  (Show)
  CONFIG VARIABLES  (Show)