Akeneo and Fomo Integration

Demonstration of how apps are integrated in WEXTL workflow builder[4]

Build marketing workflows between Akeneo and Fomo on a visual canvas. Set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.

  • 3-day trial
  • Cancel anytime
  • Up to 10 minutes quick set up
  • GDPR
  • Data Encryption
  • 2FA
  • Local Data Region

Learn about Akeneo and Fomo

Detailed info you need to know about Akeneo and Fomo integrations in WEXTL. Explore which modules apps support and how you connect them.

  • Akeneo

    • Marketing
    • 5 triggers
    • 46 searches
    • 34 actions

    Product information management (PIM) for enriching and distributing catalog data.[5]

  • Fomo

    • Marketing
    • 4 searches
    • 6 actions

    Social proof notifications that show recent customer activity on your website.[6]

How to connect Akeneo to Fomo

Set up your Akeneo and Fomo integration in 3 simple steps[2]. No coding required. Up to 10 minutes setup.

How does the integration between Akeneo and Fomo work in WEXTL?

WEXTL exposes actions and triggers for Akeneo and Fomo that help you connect apps and automate repetitive tasks[1]. A trigger is an event that happens, and an action is a step that performs when the event has occurred.

Akeneo triggersFomo actions

Akeneo modules

  • Create a File Uploads a CSV, Excel or XML file to Akeneo. Use Input Format to force an Excel format, Encoding for CSV and XML files and Separator for CSV files. Set Skip Rows to leave out leading rows.
  • Create a Job Adds a job for an uploaded file in a project, labelled with a Name and a Model Version. Attach key and value pairs through Additional Info, and note a Completion Date or Deletion Date.
  • Create a Product Adds a product to the catalog with its Family, Categories, Groups and Parent. Use Associations to link other products and Values to supply attribute data. Turn on Create Missing Options to add attribute options that do not exist.
  • Create a Product Media File Attaches an uploaded File to a Product so the media belongs to that product. Returns a User ID.
  • Create a Project Opens a project under a Name of 1 to 128 characters. Add a Description, a Help Config with Portal Video URL and Suppliers Welcome Text, and Uploaded Documents.
  • Create a Reference Entity Media File Uploads one binary File to serve as media for a reference entity or one of its records. Valid media types such as image, video or audio are accepted.
  • Create an Asset Media File Uploads one binary File to serve as the media of an asset. The file has to be a valid media type such as an image, video or audio file.
  • Delete a File Deletes an uploaded file from your Akeneo account.
  • Delete a Job Removes a single job from the jobs stored in Akeneo.
  • Delete a Product Deletes a product from the catalog by its UUID.
  • Delete a Project Removes one of the projects listed in Akeneo.
  • Delete a User Removes a user from your Akeneo organization.
  • Delete an Asset Deletes one asset from an asset family in the catalog.
  • Download a Document Fetches the file content of a project document by its ID.
  • Download a File Pulls the stored copy of a file that was uploaded to Akeneo.
  • Download a Job Output in a Chosen Format Saves what a job produced, in the format matching Format PK.
  • Download a Parsed File Gets the parsed copy of an uploaded file instead of the raw upload.
  • Download a Product Media File Downloads the binary of a media file stored on a product, found by its Code.
  • Download a Reference Entity Media File Gets the binary of a reference entity media file, found by its Code.
  • Download an Asset Media File Gets the media file of an asset, using its Asset Family Code and Code.
  • Download the Default Output of a Job Fetches the result a job produces by default, with no format to select.
  • Get a File Loads one uploaded file and reports its Name, Uploader, Upload date, Size and Status.
  • Get a Job Looks up a job by its ID and reads its Status, Step, Project and Message.
  • Get a Product Reads one product by UUID. Enable With Quality Scores to include its scores, With Completenesses for completeness data, and With Asset Share Links for share URLs.
  • Get a Product Draft Reads the draft of a product by its UUID, with the draft Family, Categories and Values.
  • Get a Product Media File Looks up one product media file by Code and reads its Original filename, Mime type, Size and Extension.
  • Get a Project Fetches a project, including its Name, Description, Steps and Available locales.
  • Get a Reference Attribute Option Returns a single option defined on a reference entity attribute, with its Code and Labels.
  • Get a Reference Entity Fetches a reference entity by Reference Code, reading its Labels and Image.
  • Get a Reference Entity Attribute Returns an attribute that belongs to a reference entity. The Type, Validation rule, Is textarea and Is rich text editor settings come with it.
  • Get a Reference Entity Record Reads a single record of a reference entity, returning its Values along with when it was Created and Updated.
  • Get a User Pulls a user profile showing the Email, Last login and whether the person Is organization admin.
  • Get a Workflow Loads a workflow by Work Flow ID, including its Code, Labels, Steps and whether it is Enabled.
  • Get an Asset Fetches an asset from an asset family. Turn on With Asset Auto Tags to include the labels of tags added by auto-tagging.
  • Get an Asset Attribute Finds an attribute of an asset family and shows its Type, plus whether it Is required for completeness or Is read only.
  • Get an Asset Attribute Option Pulls a single option from an asset family attribute together with its Labels.
  • Get an Asset Family Shows an asset family with its Naming convention, Product link rules and Transformations. Auto-tag labels join the response when With Asset Auto Tags is on.
  • Get Task Progress Reports the Status, Progress and Result of a task. Use it to check on a task after you start it.
  • Get the Default Output of a Job Returns the default output data of a job, including its Status, Stats and Completion date.
  • Get the Deleted Rows of a Job Collects the rows a job deleted, for review or later processing.
  • Get the Output of a Job in a Specific Format Reads what a job produced in the format matching Format PK. The result covers the job Status, Stats and Media archives.
  • Launch an Export Job by Code Starts an export job from its Code. Turn on Is Dry Run to test the export before a full run, and read the Job execution ID to follow it.
  • Launch an Import Job by Code Starts an import job from its Code. Use Import Mode to override the profile with Create Only, Update Only or Create or Update, and Is Dry Run for a trial pass.
  • List Asset Attribute Options Lists the options set up for an asset attribute, each with its Code and Labels. Use Limit to read fewer options.
  • List Asset Attributes Shows the attributes defined on an asset family, each with its Code, Type and Labels. Use Limit to set a maximum number of results.
  • List Asset Families Shows each asset family in the catalog with its Code, Labels and Naming convention. Use Limit to read fewer asset families.
  • List Assets by Asset Family Pulls the assets in one asset family. Use Search to filter by code or update date, Channel and Locales to restrict the values, and Limit to end early.
  • List Files Returns uploaded files showing the Name, Size and Status of each. Set After and Before for a range of upload dates, and Uploader or Uploaded Through to filter by origin.
  • List Jobs Returns jobs, each with its Name, Status, Step and Project. Use Created After, Completed Before or Status to narrow the list, and Order to sort it.
  • List Product Media Files Lists media files stored for products, each with its Code, Original filename and Mime type. Turn on With Count to add the total.

Fomo modules

  • Create an Event Adds an event to your Fomo feed so a notification can show it. Use Event Template or Template Tag to set the format, and fill IP Address to look up the city, province and country of the person.
  • Create an Event Template Defines a notification template from its Name and Message. Turn on Use Avatar for customer avatars, Use IP Mapping for location lookups or Markdown Enabled to format the text.
  • Delete an Event Removes one event from your Fomo feed, using its Event ID.
  • Get an Event Fetches one event by its Event ID, with its person, location, title, URL and image.
  • Get Statistics Reads the dashboard numbers for your Fomo application. Use From and To to limit them to a date range.
  • List Events Returns the events in your Fomo feed, one result per event. Use Limit to cap how many are read.
  • Make an API Call Calls the Fomo REST API directly with a free-form request under your saved credential.
  • Search Events Finds events that match a Value on one field. Use Search By to choose which field is compared.
  • Update an Event Edits the person, place, Title and URL of an event already in your Fomo feed. Send the Event Template of the event, since the vendor requires it on every update, and use Clear Fields to blank values and Created At to adjust its timestamp.
  • Update Application Settings Changes how the Fomo widget behaves on your site, such as its Position, Theme, Language, Display Interval and Page Load Delay. Turn on Randomize or Loop Notifications to vary or repeat what shows.

Explore alternative integrations

There are other apps[9] supported by WEXTL that can be paired with Akeneo and Fomo integrations. Pick any from the list below if the current combination isn't the one you need.

Automate Akeneo and Fomo on WEXTL®

Claim your 3-day trial to build Akeneo with Fomo integration and access every WEXTL® feature.

Cancel anytime.

Frequently asked questions

Common questions about connecting Akeneo and Fomo.

How do I connect Akeneo and Fomo?

Connect your Akeneo and Fomo accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them.[3]

What can I automate between Akeneo and Fomo?

Example: when the "Watch Files" trigger in Akeneo fires, WEXTL can "Create an Event" in Fomo. Akeneo has 5 triggers (including Watch Files, Watch Jobs, and Watch Products). Fomo has 10 actions (including Create an Event, Create an Event Template, and Delete an Event). Add filters and transforms between steps when you need them.[1]

Can Akeneo trigger actions in Fomo, and Fomo in Akeneo?

Yes. The integration works in both directions. Use the triggers of each app to start a workflow and the actions of the other app to update it.[2]

Do I need to write code to integrate Akeneo and Fomo?

No. Akeneo-to-Fomo automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic.[4]

Does Akeneo integrate with Fomo in real time?

Yes. Trigger-based automations start the moment Akeneo (or Fomo) fires a new event. Webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control.[7]

How long does it take to set up a Akeneo + Fomo integration?

A first automation typically takes 5–10 minutes: connect the credential of each app once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.

Do I need a paid plan to connect Akeneo with Fomo?

You can build your Akeneo + Fomo automation on a 3-day trial with every feature unlocked. Cancel anytime.[8]

References

List of sources used to gather information about the Akeneo and Fomo integration.

  1. Akeneo and Fomo integration source code, module specs and credentials implementation.
  2. Our Akeneo and Fomo integration documentation, structured input and output parameters, scopes, and authentication methods.
  3. Official vendor API documentation for Akeneo and Fomo, used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
  4. WEXTL® visual workflow builder, anonymized data from our technical support team.
  5. Akeneo integration information
  6. Fomo integration information
  7. WEXTL® Scheduling
  8. WEXTL® Pricing and Trial
  9. WEXTL® Apps Library

How we write our apps documentation

Explore how WEXTL® crafted Akeneo and Fomo integration page documentation. Used sources, the role of AI, and how the team validates the result.

Explore Akeneo and Fomo, or get started