Fomo MCP integration for AI agents.
Connect AI agents to Fomo through 5 structured actions, including get event, create event, and delete event. Review authentication, inputs, workflows, and sa…
- ACTION CONTRACTS
- 5
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Fomo integration exposes
The Fomo Agent App exposes 5 provider-backed actions for marketing and social work. Its current contract lets an authorized agent retrieve a single fomo event by id, create a fomo event for a configured event template, and delete an existing fomo event by id. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Fomo account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Fomo capabilities.
Showing 5 of 5 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_eventREADRetrieve a single Fomo event by ID.
INPUTS: id
create_eventWRITECreate a Fomo event for a configured event template.
INPUTS: event_type_id / event_type_tag / url / first_name / email_address
delete_eventHIGH IMPACTDelete an existing Fomo event by ID.
INPUTS: id
list_eventsREADList Fomo events with optional pagination and ordering.
INPUTS: per_page / page / order_by / order_direction
update_eventWRITEUpdate an existing Fomo event by ID.
INPUTS: id / event_type_id / event_type_tag / url / first_name
INPUT CONTRACTS
Know what the action needs before it runs.
get_event
idOPTIONAL- The Fomo event identifier.
create_event
event_type_idOPTIONAL- The Fomo event type ID.
event_type_tagOPTIONAL- The Fomo event type tag.
urlREQUIRED- The URL opened when a visitor clicks the event notification.
first_nameOPTIONAL- The first name to display in the Fomo event.
email_addressOPTIONAL- The email address associated with the Fomo event.
delete_event
idOPTIONAL- The Fomo event identifier.
list_events
per_pageOPTIONAL- The number of events to return per page.
pageOPTIONAL- The page number to return.
order_byOPTIONAL- The Fomo event sort field.
order_directionOPTIONAL- The Fomo event sort direction.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Event
Retrieve a single Fomo event by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_eventControl Create Event
Create a Fomo event for a configured event template. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_eventVerify with List Events
List Fomo events with optional pagination and ordering. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_eventsSAFETY BOUNDARY
Operate Fomo with explicit limits
- Authorize Fomo with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_event` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Fomo rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Fomo task completed successfully.
CONNECTION MODEL
API key
Fomo auth token sent with the Authorization: Token <token> header. Find it in Fomo under Settings > Site for a selected website: https://docs.fomo.com/reference/fomo-api-auth-token
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Fomo.